Skip to content
DocumentationUse source transactions
On this page

Page resources

Open Markdownllms.txtView source

Last updated

This recipe changes one project without creating hidden manifests or merging workspace roots. Commands and source are illustrative end-product syntax.

Declare a workspace

One
one 1

semantic acme.workspace
    domain one.project@1
    workspace Acme@1
        project ./parcelhub
        project ./support-triage

Each project retains its own one.one, lock, roots, plans, artifacts, authority, and History.

Propose a package change

Console
one package add acme.commerce@1 --project parcelhub
one inspect source-transaction:sha256:…
Plain text
base source sha256:old…
patch parcelhub/one/contracts.one
lock parcelhub/one.lock sha256:new…
affected roots parcelhub_embedded, parcelhub_orders_desk

Commit only against current bases

Console
one check --project parcelhub
one test --project parcelhub
one source apply source-transaction:sha256:…

A stale base rejects instead of silently rebasing. Structured editor views use the same source transaction and never persist a second semantic model.

Format without changing unknown bodies

Console
one fmt parcelhub/one/contracts.one

The envelope and known semantic regions format canonically. Unknown implementation-language bodies remain byte-preserved.

Structured editor views use the same transaction

A form, table, graph, or combined view in an editor proposes a bounded patch set against the exact source revision, reparses every affected input through the single owned parser, reruns the required owner checks, and commits one ordinary undoable source transaction only when every base revision still matches. It never writes a hidden semantic model or silently rebases a stale edit. See editors and language tooling and the lock.

Executable evidence

one-project owns the crash-safe source/lock transaction, and one-lsp owns the preview/commit language-server transcript tests:

Console
cargo test -p one-project --lib complete_transaction_retains_canonical_owner_evidence
cargo test -p one-lsp

The workspace, package, and command forms above remain illustrative end-product syntax.

See project and workspace and source and meaning.