Specification

Specification

The pwcli-core architecture has two engines:

• Dynamic overlay: natural-language input, intent classification, candidate panel selection, clarification, and summaries.
• Static bedrock: routes, schemas, databases, registered panels, typed tools, approvals, audit logs, source records, and fallback views.

State Machine

State A: Console
  Human input is accepted as lossy text, voice, or gesture.

State B: Intent Telemetry
  The system compiles input into intent.schema.json.

State C: Hydrated Panel
  A registered primitive receives deterministic backend data.

State D: Approval Gate
  Required for state-changing or permission-sensitive actions.

State E: Return Focus
  The panel collapses into the command stream with a concise artifact.

State F: Static Fallback
  Low confidence or explicit user request opens a deterministic route.

Output Hierarchy

1. Source schema and standards crosswalk.
2. Deterministic bedrock configuration.
3. Primitive registration.
4. Intent orchestration logic.
5. Typed sandboxed execution layer.

Canonical source: https://github.com/Protocol-Wealth/pwcli-core/blob/main/SPEC.md