Infrastructure for infrastructure, at the terminal

HUMΛN’s moat compounds when every new agent starts from governed defaults — not from five internal apps worth of copy-paste. Wave 7 is the story of the CLI as co-equal product: manifests, validators, and templates that wire human.call, Capture, feedback, and effective config reads.

Validate before you fantasize

human humanos-manifest validate against a humanos.agent.v1 manifest is the smallest green path: apiVersion, primitive hooks human_call, capture, feedback set true. CI can run it; humans can run it; agents can run it. The validator is intentionally minimal today — schema strictness grows as manifests mature.

Turn-chat vs duplex templates (where we are headed)

Scaffolds (A) and (B) from the program plan split request/response agents from event-driven agents, wiring InteractionContext for duplex without dragging MediaRecorder into every repo. We ship validate and scaffold; templates expand as APIs harden.

Use cases

Given a hackathon starter repo, when a dev runs validate, then they know their manifest declares governed hooks before codegen.
Given platform CI, when validate fails, then merges block drift from HumanOS primitives.
Given a founder demo, when someone bootstraps in ten minutes, then the story is intent, not glue.

Rule of Threes: Great for the human (fast safe start), sustainable for HUMΛN (consistent platform), and better for humankind (fewer unauditable one-offs).

Extended narrative — validate, then scaffold

human humanos-manifest validate is the bouncer: apiVersion, human_call, capture, feedback hooks must be true — no “we will add governance later” in CI. humanos-manifest scaffold emits humanos.agent.v1.min.yaml plus turn-chat and duplex TypeScript stubs that point to real integration seams (human.call, captures, events) instead of cloning companion hacks.

This is Infrastructure for Infrastructure: the tenth agent should not rediscover the same five HTTP calls. Scaffolds are allowed to be minimal; they are not allowed to lie about what is governed.

Trust expectation: A new repo starts honest — manifest declares hooks; stubs link to platform APIs.

Given / When / Then (use case 4)

Given CI running validate on PR, when a teammate removes capture: true, then the build fails before merge.

Given / When / Then (use case 5)

Given a duplex agent repo, when a dev opens src/duplex.ts, then they see guidance toward interaction/SSE — not MediaRecorder copy-pasta.

Given / When / Then (use case 6)

Given a founder demo clock of ten minutes, when they run scaffold + validate, then they have a governed tree to extend — not a blank README prayer.