Applicable Convention · CI-0011

2HE CLI

The canonical repository command interface turns one intent-level command into a visible, validated technical workflow.

Open canonical Markdown Guide generation

Current commands

`2he repo status`

Safe default. Shows repository branch, working-tree state, and whether the Pages output exists.

`2he repo bootstrap sync [target]`

Installs the exact global pointer in root AGENTS.md and keeps repository-only rules in root Internal-AGENTS.md.

`2he repo bootstrap audit [target]`

Fails if the pointer or repository-internal file boundary is missing, stale, or mixed.

`2he pages build`

Generates and validates the Guide Platform in _site/.

`2he pages update`

On main: fast-forward pull, build, validation, commit of current non-ignored changes, push, and Pages deployment trigger.

`2he cache idea`

Captures an idea as a non-canonical living record for later review.

`2he chat transcript`

Saves a verified, immutable raw Codex-session snapshot under Git-ignored .temp/ with a UTC datetime at the end of its filename.

`2he chat xrt publish`

Publishes separate private raw and semantic XRT evidence, registers both resolvers, and verifies device-independent retrieval.

`2he chat xrt lookup`

Discovers related durable handovers by entity, area, project, or topic.

Connect a new repository once

When the shared CLI is available, run 2he repo bootstrap sync from the new repository. Otherwise download the canonical seed once:

curl -fsSL https://fhxfhx.github.io/2HE__Ecosystem/bootstrap/AGENTS.md -o AGENTS.md

Create Internal-AGENTS.md with the repository-specific rules, then commit both root AGENTS.md and Internal-AGENTS.md. Every later Codex session and Codespace opened from that repository discovers the same 2HE entry point automatically.

Component Conventions

The authoritative 2HE-CLI Component definition remains in Components/2HE-CLI. These bindings govern the separate implementation Workbench.

Ecosystem Binding Authority and relationship between the Ecosystem and the implementation Workbench Command Grammar 2he <domain> <command> [target] [options] Workbench Bootstrap Required context and binding for implementation work

Initial Codespaces setup

git pull
chmod +x 2he
./2he repo status

The executable permission is a one-time setup for the repository wrapper. After that, use ./2he directly.

One-command publication

./2he pages update

Optional custom commit message:

./2he pages update -m "Describe the Convention Increment"

Scope warning: publication stages all current non-ignored repository changes. Review ./2he repo status first when unrelated work may be present.

One-intent end-to-end execution

2HE DO <Target>

This conversational control phrase authorizes the repository participant to complete the scoped target through implementation, validation, workspace maintenance, commit, push, applicable Pages deployment, and external verification. It uses the 2he executable; it does not introduce a second CLI grammar.

Open the Pages CRUD lifecycle.

State boundary

Build→Validate→Commit→Push→Deploy trigger→Deploy→Verify

2he pages update completes through push and reports the deployment trigger. GitHub Actions owns deployment; external verification remains a separate state.