Skip to content

Adopt deferred CLI noun namespaces (policy-gated surface growth) #59

Description

@mdheller

Follow-up from #57 / #58. cc @mdheller.

The 3x3 build-recipe contract and the CLI-surface reconciliation landed in #58. That PR reconciled the full spec command tree onto the canonical verb model in `docs/CLI_SURFACE_POLICY.md` and adopted only the nouns that have a real delegate today: `build`, `vocab`, `search`, `agents`.

The remaining spec nouns are recorded as `deferred` in `manifests/cli-surface.json` and, per the phase-1 policy, are not scaffolded (empty subtrees are forbidden):

`context`, `config`, `fs`, `graph`, `docker`, `conda`, `minio`, `rsync`, `kafka`, `work`, `gib`, `opencog`, `genesis`, `inception`, `twin`, `bridge`

What adoption requires (per noun)

  • A real delegated tool/engine (no scaffolds).
  • Resolution to canonical read/mutation/runtime/bootstrap verbs only — no competing command language.
  • Flip `status: adopted` with a `delegate` + `verbs` in `manifests/cli-surface.json`; `scripts/validate_cli_surface.py` then enforces it.

Adopt incrementally as delegates become real. Surface growth is policy-gated.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions