A business-software language that belongs to the developer.

Safire language source is intended to be readable, explicit and suitable for long-lived business applications — while the IDE provides the productive visual working experience on top.

Source-first ownership

Readable source is the canonical application truth.

The language is the foundation beneath SafireIDE, designers, controls, data bindings, services and application logic.

Human-readable application source.
Strong business-oriented type and runtime model.
Classes, procedures, modules and application services.
Controls and windows represented through Safire semantics.
Compiled/runtime architecture without requiring ordinary application developers to use C++.

customer_maintenance.sf — illustrative Safire style

Window CustomerMaintenance
    Title = "Customer Maintenance"

    Entry CustomerName
        Bind = Customer.Name
        Required = True
    End

    Button SaveButton
        Text = "Save"
    End
End

Event SaveButton.Click
    If Customer.Validate()
        Customer.Save()
    End
End

Progressive depth

Productivity when the default is enough. Precision when it is not.

RAD

Business / RAD API

High-level Window, Form, Browse, Binding, Validation and business-oriented objects.

PLAT

Platform API

Desktop services such as Canvas, Image, Printer, Clipboard, Timer and native dialogs in Safire form.

NATIVE

Advanced native API

A deliberate escape hatch for framework and component developers who need deeper platform access.

Language + environment

The language is the foundation. The environment is the product.

A productive business development system needs more than syntax. Safire language concepts connect into compiler services, data, controls, testing, project metadata, Source Vault and AI knowledge.

TYPE

Types

Business data types, records, collections and objects.

FLOW

Logic

Procedures, methods, modules, control flow and error handling.

DATA

Data

Database and query abstractions designed for business applications.

UI

Window, control, event and binding semantics owned by Safire.

AI knowledge

AI should know the installed language — not guess it.

Safire can expose machine-readable language, runtime, control and diagnostic metadata so AI works against the actual installed platform version.

See the AI architecture

Safire knowledge sources

language grammar
symbols and types
runtime objects
control properties
control events
compiler diagnostics
project schemas
test APIs
build / package tools
version + deprecation metadata

Readable enough for people. Structured enough for tools.

Safire source remains the common ground beneath visual RAD and optional AI.

Review documentation