Skip to content

v0.7.0 — the seven verbs

Choose a tag to compare

View all tags
@nabsha nabsha released this 01 Aug 02:15
v0.7.0
0a0c537
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

YarraMate 0.7.0 — the seven verbs

A clean break: the CLI is now exactly one verb per lifecycle stage, designed top-down as the agent-harness contract (docs/AGENT-INTERFACE.md, ADRs 0056–0061).

init → design → apply → ask → check → reconcile → export
create  fill    write   read  gate    drift       derive

New

  • yarramate design — the conception loop's ask-half (ADR 0058): each stateless invocation serves exactly the top open design question — materiality-ordered from an internal, versioned catalogue (29 questions across motivation/business/application/hygiene waves) — with the subject's one-hop brief slice and per-wave progress. Answer, apply, re-run; resumable across sessions and agents because nothing is stored but the model.
  • yarramate apply — all writes as one validated atomic batch (yarramate/operations/v1, ADR 0057): any invalid operation rejects the whole batch; documents are addressed by workspace-manifest paths; edits are enrich-only (scalars replace, lists append).
  • yarramate ask — every consumed-now read behind one yarramate/ask-result/v1 envelope (ADR 0059): bare orientation (check verdict + drift + open questions + dependency-ordered backlog), free-text addressing (ask <ws> "billing" → matching concepts seed a one-hop brief), --subjects roster, --kinds declarable vocabulary, --advise (engine-composed slice + open questions + drift for the LLM to answer as the architect), --next, --open, --compare.
  • yarramate export — every persisted artifact (ADR 0060): graph (canonical v2 JSON), markdown, briefs (a handoff bundle: one brief per projected concept + INDEX.md), likec4 (delegates to the sibling adapter binary in a separate process).
  • Adequacy machinery (ADR 0056): linkage-depth trigger conditions and attestation claims (yarramate/attestation/<topic>), keeping "filled adequately" structural and git-reviewed — the engine still never reads words.

Removed (no aliases — ADR 0061)

add, connect, new, compile, view, context, status, next, compare, evidence, interrogate.

Before Now
add / connect one apply batch
new projection author the projection file directly; check validates it
status ask
context (all forms) ask <slice> (brief by default; --budget digest; --json envelope)
next / compare / interrogate ask --next / --compare / --open
compile / view export graph / export markdown
evidence reconcile reports; check --strict gates

Changed

  • Core contract declares exactly the seven commands; status-result/v1 and next-result/v1 formats, schemas, and package exports are gone (their content lives in ask-result/v1).
  • MCP server re-exposed as four read-only tools: yarramate_ask, yarramate_design, yarramate_check, yarramate_reconcile.
  • init pointer, the agent skill, README, and all reference docs rewritten to the seven-verb surface.
  • New package schema exports: ./schema/operations, ./schema/apply-result, ./schema/design-step, ./schema/ask-result.

The repository's own architecture model was maintained through these verbs while they were built: every self-model change in this release landed as an apply batch and was read back through ask.

Assets 2
Loading