EXPLICIT RELATIONSHIPS, BOUNDED EFFECTS

A language for
the meaning around code.

The semantic model

ConceptQuestionExample
EntityWhat exists?An input, a generated file, a receipt
ActivityWhat transformation occurs?Generate, compare, observe
AgentWho acts?A person, service, or implementation agent

Relationships such as used, wasGeneratedBy, wasDerivedFrom, and wasAssociatedWith retain the connection between an operation and its origin.

Generation is not authority

.gooo declaration
    -> semantic IR
    -> generated Go or a bounded candidate
    -> native observations and receipts
    -> a decision with an explicit scope

A generated candidate does not grant permission to write to the input project. A deterministic replay does not prove every semantic property. A successful development-branch check does not publish a release.

Self-improvement, one operation at a time

The development branch includes coordinated syntax registration and bounded code-transformation execution. Their inputs, generated members, native checks and replay observations remain connected. They do not constitute unrestricted invention of new syntax.

Gooo is not currently a general-purpose replacement for Go. General execution, arbitrary safe refactoring, production readiness, and external usefulness must not be inferred from a passing internal example.

For people and agents

A person can read the intent. An implementation agent can operate within a declared scope. A verifier can compare the actual result with the contract. The common object is an explicit operation and its evidence, not an unstructured claim of success.

Understand the evidence model →