Schema and sources

The CLI reads schema; it never writes it. Objects are declared in code and applied with schema.sync from @stndrds/client. There is no schema push. From a terminal you can list objects, inspect one, list and remove the sources that declared them, and diff the deployed source against the shared runtime.

Inspect the deployed schema

standards schema list

standards schema inspect contacts

inspect accepts an object name or id and returns its attributes, types and views.

List and remove sources

A schema source is a codebase that pushed definitions through @stndrds/client. sources list shows each source's id, hash, last apply time and object names.

standards sources list

Removing a source demotes its objects to custom objects. Records are kept.

standards sources remove <sourceId> --yes

The command refuses to run without --yes.

Pull

pull reads the deployed source and the shared runtime, then prints reconciliation guidance. It writes no file and changes nothing in the workspace.

standards pull

standards pull --json

--json prints the canonical shared state instead of the guidance. Both forms only see what has been applied: unbuilt local TypeScript is not part of the comparison.

Diff

diff compares the deployed source with the shared runtime and lists every change, addressed by object, attribute, relation, view or content name.

standards diff

standards diff --json

Use it as a CI gate:

standards diff --json
case $? in
  0) ;;
  1) echo "runtime drifted from source"; exit 1 ;;
  *) echo "diff failed"; exit 2 ;;
esac

Runtime additions and replaced contents stay listed until you reconcile them. Deploying new builders alone does not clear them.

Next steps

• Schema sources: what a source owns and what happens on removal.
• Sync: apply the schema you declared in code.
• CLI: exit codes and output formats.