Skip to content

Home

Jump to bottom
Nick Rygiel edited this page Jul 4, 2026 · 6 revisions

pwcli-core Wiki

pwcli-core is an open specification for building intent-driven, dual-engine applications: a conversational or CLI-style intent surface backed by deterministic routes, schemas, registered panels, typed tools, provenance, and approval gates.

Start Here

  • Specification - architecture model, state machine, trust boundary, and output hierarchy.
  • Standards Map - maturity map for open standards, protocols, conventions, and local patterns.
  • Schemas - intent, primitive, route, execution, source, provenance, rights, crosswalk, context-pack, agent-card-lite, runtime-adapter, and redaction-policy schemas.
  • Open Data and Crosswalks - OAI-PMH, Dublin Core, MARC 21, schema.org, DCAT, IIIF, and rights-aware ingestion.
  • Security and Trust Boundaries - AI may/may-not rules, source assertions, approvals, provenance, and poisoning defense.
  • Context Packs - versioned Markdown operating context with YAML frontmatter.
  • Architecture Engine Prompt - canonical system prompt for pwcli-core design tasks.
  • Companion Projects - related Protocol Wealth open-source references.
  • Validation - local and CI checks for schemas, crosswalks, context packs, runtime adapters, redaction policies, links, and metadata.
  • Agent Runtime Adapters - how existing agent infrastructure fits under the pwcli-core policy envelope.
  • Privacy and Redaction Control Plane - data classes, redaction stages, and policy metadata.
  • Agent Poisoning Defense - prompt injection, untrusted input, secret isolation, egress, and workflow controls.
  • Human UX Guide - progressive disclosure, preview metadata, and approval friction.
  • Turn Based Game Demo - runnable no-build example for intent telemetry, registered primitive hydration, approval, and ledger output.
  • Adapter Control Demo - runnable no-build example for untrusted input, adapter selection, redaction policy, approval, provenance, and run receipts.
  • Roadmap - practical next implementation steps.

Core Principle

Human language is lossy. Production systems are not.

pwcli-core compiles fuzzy user intent into structured telemetry, then selects registered primitives, deterministic routes, and typed execution targets. If confidence is low or the user wants a traditional view, the system falls back to a static route instead of inventing behavior.

Repository

Clone this wiki locally