Canonicalize Passpod Specification v0.1

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +1,42 @@
-## Public TASK repo checklist
-
-- [ ] No private customer data
-- [ ] No production keys
-- [ ] No scoped key internals
-- [ ] No buyer-specific workflows
-- [ ] No commercial backend logic
-- [ ] Example receipts are sanitized
-- [ ] `bash tools/check-public-task-repo.sh` passes
+## Passpod v0.1 checklist
+
+### Scope
+
+- [ ] Change is bounded and described.
+- [ ] Unrelated files are not modified.
+- [ ] Active architecture is not redesigned unintentionally.
+
+### Canonical semantics
+
+- [ ] Preserves `PROPOSE -> CHALLENGE -> AGREE -> CLOSE`.
+- [ ] Preserves transport neutrality.
+- [ ] Preserves append-only history.
+- [ ] Preserves immutable accepted messages.
+- [ ] Preserves terminal closure.
+- [ ] Profiles do not redefine core message meanings.
+
+### Implementation
+
+- [ ] Existing schemas remain authoritative for structure.
+- [ ] Semantic validator remains authoritative for bounded protocol validity.
+- [ ] SDK and CLI do not introduce new semantics.
+- [ ] No unsupported transport, persistence, signature, cryptographic, or identity claims are added.
+
+### Validation
+
+- [ ] `PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests`
+- [ ] `bash tools/check-public-task-repo.sh` (Passpod v0.1 repository gate)
+
+### Security and privacy
+
+- [ ] No secrets, credentials, private keys, tokens, or private pilot records.
+- [ ] No sensitive local files.
+- [ ] Inspection output does not expose full private payloads.
+- [ ] No new network behavior unless explicitly scoped in a later approved transport pass.
+
+### Documentation
+
+- [ ] Active terminology matches Passpod v0.1.
+- [ ] Archived terms appear only in migration or historical context.
+- [ ] Links and commands are verified.
+- [ ] Claims do not overstate production readiness, adoption, certification, cryptography, or deployment.

.github/workflows/validate.yml

@@ -1,4 +1,4 @@
-name: Validate TASK public repo
+name: Validate Passpod v0.1
 
 on:
   pull_request:
@@ -9,16 +9,34 @@ permissions:
   contents: read
 
 jobs:
-  validate:
+  validate-passpod:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - name: Install validator dependencies
-        run: python -m pip install -r requirements.txt
-      - name: Validate JSON and public repo gate
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install Python dependencies
+        run: python3 -m pip install -r requirements.txt
+
+      - name: Check canonical JSON files parse
         run: |
-          python -m json.tool schemas/trust-action-receipt.schema.json >/dev/null
-          python -m json.tool examples/remote-worker.receipt.json >/dev/null
-          python -m json.tool examples/agent-freeze.receipt.json >/dev/null
-          python -m json.tool examples/refund-review.receipt.json >/dev/null
-          bash tools/check-public-task-repo.sh
+          set -euo pipefail
+          for json_file in \
+            schemas/message.schema.json \
+            schemas/handshake.schema.json \
+            schemas/profile.schema.json \
+            examples/valid/*.json \
+            examples/invalid/*.json
+          do
+            python3 -m json.tool "$json_file" >/dev/null
+          done
+
+      - name: Run Python test suite
+        run: PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests
+
+      - name: Run Passpod v0.1 repository gate
+        run: bash tools/check-public-task-repo.sh

ADOPTION.md

@@ -1,19 +1,96 @@
-# Adopting Passpod TASK Core
+# Adoption
 
-Passpod TASK Core is a public draft standard proposal for Sensitive Action Control.
+This document explains how an evaluator, implementer, standards participant, or potential pilot partner can assess Passpod without assuming established adoption.
 
-Vocabulary: Sensitive Action Control, Trust Action Receipt, No receipt, no sensitive action, Passpod TASK Core.
+Passpod is a transport-neutral standard and handshake protocol for structured trust negotiation. The canonical flow is:
 
-## Reader paths
+```text
+PROPOSE -> CHALLENGE -> AGREE -> CLOSE
+```
 
-- Developer: inspect the schema, examples, OpenAPI reference, and validator to understand the public receipt model.
-- Security reviewer: review the demo-vs-production boundary, threat model, and public/private exclusions.
-- Pilot buyer: use the public repo to evaluate the standard, then request scoped Passpod Hub access through the Pilot Access Engine.
-- Standards/community reader: evaluate Sensitive Action Control, Trust Action Receipt semantics, and Passpod Protocol doctrine without relying on private product internals.
+Adoption in this document means evaluation, experimentation, implementation, interoperability exploration, workflow-fit analysis, Profile design, or conformance feedback. It does not imply customers, ecosystem adoption, market traction, production deployment, or formal standards recognition.
 
-## Boundary
+## Adoption Paths
 
-This repository proves the public standard and test layer. It does not expose
-the full Passpod Hub product, production issuer logic, scoped key generation,
-customer workflows, private commercial logic, Sentinel/Ops internals, or an
-exit roadmap.
+### 1. Read The Specification
+
+Start with:
+
+- [README.md](README.md)
+- [docs/STANDARD.md](docs/STANDARD.md)
+- [docs/PROTOCOL.md](docs/PROTOCOL.md)
+- [docs/STATE-MODEL.md](docs/STATE-MODEL.md)
+- [docs/MESSAGE-MODEL.md](docs/MESSAGE-MODEL.md)
+- [docs/PROFILES.md](docs/PROFILES.md)
+- [docs/CONFORMANCE.md](docs/CONFORMANCE.md)
+
+The Standard remains the semantic authority. The protocol, state model, message model, Profiles model, and conformance model explain how the architecture is interpreted.
+
+### 2. Run The Reference Implementation
+
+Use the local reference implementation to inspect the current repository behavior:
+
+- [docs/QUICKSTART.md](docs/QUICKSTART.md)
+- [schemas/](schemas/)
+- [examples/valid/](examples/valid/)
+- [examples/invalid/](examples/invalid/)
+- [validator/semantic_validator.py](validator/semantic_validator.py)
+- [passpod/](passpod/)
+- [passpod/cli.py](passpod/cli.py)
+
+The reference implementation is minimal and transport-neutral. It is useful for evaluation, fixtures, SDK behavior, CLI inspection, and validator feedback. It is not a production transport or hosted service.
+
+### 3. Evaluate A Workflow
+
+An evaluator may model an existing negotiation as:
+
+```text
+PROPOSE -> CHALLENGE -> AGREE -> CLOSE
+```
+
+This can help identify participants, evidence expectations, constraints, agreement boundaries, and terminal outcomes. The repository does not prescribe business outcomes.
+
+### 4. Explore A Profile Candidate
+
+Domain-specific roles, evidence expectations, constraints, terminology, workflow guidance, and terminal interpretations belong in Profiles.
+
+No active Reference Profile is currently implemented. A Profile candidate should preserve the Standard, the Handshake Protocol, append-only history, immutable accepted messages, and terminal closure.
+
+### 5. Participate In Passpod Pilot
+
+Passpod Pilot is the controlled evaluation path for workflow fit, handshake modeling, Profile candidate discovery, implementation feedback, evidence expectation discovery, conformance questions, and developer experience feedback. See [PILOT_ACCESS.md](PILOT_ACCESS.md).
+
+Pilot work does not automatically change the Standard. Any normative change requires intentional architectural review.
+
+## Adoption Maturity
+
+Current status:
+
+- Passpod Specification v0.1 is conceptually frozen.
+- A minimal transport-neutral reference implementation exists.
+- No production transport binding is included.
+- No active Reference Profile is implemented.
+- No certification program is defined.
+- No conformance certification program exists.
+- No guaranteed interoperability is claimed.
+- No published package is assumed.
+- No adoption metrics are claimed.
+
+The existing test suite demonstrates repository behavior. It is not evidence of market adoption, production use, pilot acceptance, or standards-body recognition.
+
+## Unsupported Commitments
+
+This repository currently does not provide:
+
+- production SLA;
+- hosted service;
+- deployment support;
+- commercial support commitment;
+- certification;
+- cryptographic trust;
+- identity verification;
+- persistence;
+- HTTP API;
+- formal standards-body process.
+
+These are not promised future products in this document.

CHANGELOG.md

@@ -1,5 +1,49 @@
 # Changelog
 
-## v0.1.0
+## Unreleased
 
-Initial public draft structure.
+### Added
+
+- Passpod Standard, Handshake Protocol, State Model, Message Model, Profiles model, Conformance model, and Terminology documents for Passpod Specification v0.1.
+- Specification freeze report documenting internal consistency of the canonical v0.1 architecture.
+- Canonical machine-readable schemas for messages, handshakes, and profiles.
+- Valid and invalid fixtures for the canonical handshake and profile model.
+- Semantic validator for structural and protocol-level validation.
+- Reference Python SDK value objects for messages, handshakes, profiles, and validation errors.
+- SDK fixture round-trip coverage for canonical examples.
+- CLI `validate` and `inspect` commands.
+- Developer quickstart for local tests, validation, inspection, and SDK usage.
+- Passpod v0.1 repository gate.
+- Canonical CI validation for JSON parsing, unit tests, and the repository gate.
+
+### Changed
+
+- README migrated to present Passpod v0.1 as a transport-neutral specification and handshake protocol.
+- Repository positioning migrated to a combined Passpod specification repository with a reference Python SDK.
+- CI and pull request checks migrated from TASK-era requirements to Passpod v0.1 architecture checks.
+- Governance, security, contribution, and conduct documents migrated to current Passpod v0.1 terminology and authority boundaries.
+
+### Archived
+
+- Legacy receipt schema and receipt examples moved into the legacy archive.
+- Legacy OpenAPI and worker-reference material moved into the legacy archive.
+- Legacy TASK-era specification, roadmap, and launch-readiness documents moved into the legacy archive.
+
+See [archive/legacy-task/README.md](archive/legacy-task/README.md) for archive context. Archived materials are historical and do not define active Passpod v0.1 compatibility.
+
+### Security
+
+- Repository gate preserves checks for secrets, private keys, sensitive local files, and private operational data patterns.
+- CLI inspection output is bounded and does not dump full message payloads, evidence references, extensions, sender payloads, or recipient payloads.
+
+## Historical TASK-Era Tags
+
+These tags predate the Passpod v0.1 architectural reset. They are retained as repository history and do not represent a Passpod Specification v0.1 release.
+
+### v0.1.1
+
+- Public validation and launch-readiness checkpoint for the earlier TASK Core architecture.
+
+### v0.1.0
+
+- Initial public draft structure.

CODE_OF_CONDUCT.md

@@ -1,3 +1,7 @@
 # Code of Conduct
 
+This applies to Passpod as a specification and reference implementation repository.
+
 Be respectful, practical, and security-conscious.
+
+This document does not assign an enforcement contact or authority. That path remains a project-governance question.

COMMERCIAL_BOUNDARY.md

@@ -1,38 +1,60 @@
 # Commercial Boundary
 
-This repository is public proof for Passpod TASK Core.
+This document separates the open Passpod specification and reference implementation from possible future commercial activity.
 
-It helps developers and reviewers inspect the public standard/test layer:
+It does not define current pricing, service plans, hosted availability, commercial commitments, customers, revenue, partners, or deployment status.
 
-- Trust Action Receipt schema;
-- public demo receipts;
-- local validator;
-- public OpenAPI reference shape;
-- basic doctrine for Sensitive Action Control.
+## Open Repository Boundary
 
-## Product stack
+This repository currently contains:
 
-Passpod TASK Core -> Passpod Hub -> Control Packs -> Pilot Access -> paid pilot / Team / Enterprise.
+- normative specification documents;
+- canonical schemas;
+- valid and invalid fixtures;
+- semantic validator;
+- reference Python SDK;
+- CLI;
+- tests;
+- governance and developer documentation;
+- migration archive material.
 
-- Passpod TASK Core is the public standard/test layer in this repo.
-- Passpod Hub is the paid hosted product layer and is not included here.
-- Control Packs are AgentTrust and Remote Worker Trust.
-- Pilot Access Engine is the scoped access path for authorized hosted access.
-- DIDX is the company, legal, and registry anchor.
+The repository's rights and conditions are defined by [LICENSE](LICENSE). This document does not add license grants or restrictions.
 
-## Not in this repo
+The open repository is sufficient to read the current specification, run the reference implementation, inspect fixtures, and evaluate the canonical handshake model locally.
 
-This repo does not expose:
+## Possible Future Commercial Activity
 
-- production issuer logic;
-- production signing internals;
-- scoped key generation;
-- Passpod Hub internals;
-- customer workflows;
-- private commercial strategy;
-- Sentinel/Ops internals;
-- exit roadmap.
+Possible future commercial services could include:
 
-Public demo receipts are not production-valid receipts. Production-valid
-receipts require authorized issuer access through Passpod Hub and the Pilot
-Access Engine.
+- implementation assistance;
+- integration support;
+- Profile design assistance;
+- pilot facilitation;
+- hosted transport bindings;
+- managed validation;
+- operational support;
+- enterprise support.
+
+These are possibilities, not current offerings. This document does not state prices, plans, availability, service levels, launch dates, or acceptance criteria.
+
+## Separation From The Standard
+
+Commercial services must not silently redefine:
+
+- the Passpod Standard;
+- the Handshake Protocol;
+- message semantics;
+- conformance;
+- Profile rules.
+
+A hosted or commercial implementation is not automatically normative. Paid access is not required for understanding or implementing the open specification.
+
+## Current Commercial Status
+
+This repository does not define current pricing, service plans, hosted availability, or commercial commitments.
+
+It does not claim production deployment, production readiness, active customers, revenue, funding, negotiations, partnerships, grants, investors, or enterprise support.
+
+## Archived Model
+
+Archived TASK-era materials described Hub, Pilot Access Engine, scoped-key, and receipt-service concepts. Those concepts are retained for provenance in archive material only and are not part of the current Passpod v0.1 architecture.