PTSIP 0.3.8a2__tar.gz → 0.3.8a3__tar.gz

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PTSIP
-Version: 0.3.8a2
+Version: 0.3.8a3
 Summary: Reference tooling for primary lifecycle ownership and responsibility isolation
 Author: Kinirin
 Maintainer: Kinirin
@@ -42,8 +42,8 @@ Dynamic: license-file
 
 # PTSIP — Primary Lifecycle Ownership and Responsibility Isolation Policy
 
-**Status:** Tool `0.3.8a2` repository-namespace stabilization prerelease — publication pending<br>
-**Tool/package version:** `0.3.8a2`<br>
+**Status:** Tool `0.3.8a3` Context Plane migration-semantics emergency prerelease — publication pending<br>
+**Tool/package version:** `0.3.8a3`<br>
 **Project Profile contract:** `pp.1.02`<br>
 **Specification family:** `0.3.7-draft`<br>
 **Bound immutable Specification revision:** `3c47816770d194ae42f98faedc911d980db0e62a`<br>
@@ -55,11 +55,11 @@ PTSIP is a project-defined architecture policy for separating project responsibi
 
 > **Purpose precedes reuse.** Classify a coherent responsibility by why it exists and which lifecycle owns it before optimizing for code sharing.
 
-Tool `0.3.8a2` is a repository-namespace stabilization prerelease built on the already-published `0.3.8a1` bridge and the same frozen Specification binding. It preserves the proposed-candidate bridge while establishing `.ptsip/` as the canonical repository-local ownership boundary for PTSIP-managed contracts, registries, configuration, task/operation metadata, and execution state. Canonical repository indexes use JSON. This release reserves Task and runtime namespaces but does not claim a completed generic Task Engine, Go runtime, or Tool `0.4.0` capability-recovery implementation.
+Tool `0.3.8a3` is an emergency corrective prerelease over the published `0.3.8a2` repository-namespace release. Tool `0.3.8a2` established `.ptsip/` and the provider-neutral Context Plane at repository level, but its Context Projection implementation remained under `developer/automation/` and therefore was not shipped in the installed Consumer Tool. Tool `0.3.8a3` closes that packaging and migration gap by shipping the canonical Context Plane implementation as `ptsip.context_plane`, exposing `ptsip context status|migrate|repair|check`, and binding release verification to the installed wheel. The Specification and Project Profile identities remain unchanged.
 
 ## Primary lifecycle ownership
 
-Canonical Tool `0.3.8a2` classifications remain exactly:
+Canonical Tool `0.3.8a3` classifications remain exactly:
 
 | Classification | Meaning |
 | --- | --- |
@@ -81,9 +81,9 @@ TOOLCHAIN
 NEUTRAL_CONTRACT
 ```
 
-Tool `0.3.8a2` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
+Tool `0.3.8a3` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
 
-Tool `0.3.8a2` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
+Tool `0.3.8a3` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
 
 ## Classification is not path or technology
 
@@ -104,7 +104,7 @@ Paths such as `tests/`, `tools/`, `deploy/`, `ops/`, or `.github/workflows/` are
 
 ## Responsibility Map v2
 
-Tool `0.3.8a2` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
+Tool `0.3.8a3` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
 
 ```text
 classification
@@ -233,12 +233,12 @@ Upgrade to the latest **published** release:
 python -m pip install --upgrade PTSIP
 ```
 
-Tool `0.3.8a2` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
+Tool `0.3.8a3` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
 
 After publication, install this prerelease explicitly with:
 
 ```powershell
-python -m pip install "PTSIP==0.3.8a2"
+python -m pip install "PTSIP==0.3.8a3"
 ```
 
 For source development on this release line:
@@ -261,6 +261,8 @@ ptsip clarify .
 ptsip gate .
 ptsip resolve --help
 ptsip conform .
+ptsip context status . --json
+ptsip context check . --json
 ```
 
 New project-owned profiles are selected through `.ptsip/profiles/index.json`; the catalog's `default_profile` resolves the active `*.ptsip.yaml` resource. Repository-root `ptsip.yaml` remains a compatibility/migration input, and an explicit `--profile` path still takes precedence.
@@ -269,7 +271,7 @@ New project-owned profiles are selected through `.ptsip/profiles/index.json`; th
 
 Repository evidence is not architecture authority. Candidate discovery, path names, templates, heuristics, and agent confidence can support review but cannot manufacture project intent.
 
-Canonical Tool `0.3.8a2` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
+Canonical Tool `0.3.8a3` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
 
 ```text
 classification
@@ -279,7 +281,7 @@ runtime_required
 executable
 ```
 
-The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a2` ownership authority.
+The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a3` ownership authority.
 
 Example dry-run:
 
@@ -344,7 +346,7 @@ PTSIP uses action-time synchronization rather than continuous background polling
 
 Artifact ownership is independent from producer ownership. A `DEVELOPMENT_TOOLING` or `DELIVERY` component may validly build a `PRODUCT` artifact, but the resulting artifact must still satisfy the Product package boundary.
 
-Tool `0.3.8a2` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
+Tool `0.3.8a3` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
 
 ## VPMS — Verification Purpose Management System
 
@@ -360,7 +362,7 @@ VPMS
 
 PTSIP classification and VPMS Verification Purpose remain separate axes. PTSIP core does not depend on VPMS. VPMS consumes only a narrow read-only projection of already-resolved PTSIP metadata.
 
-The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a2` PTSIP classification.
+The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a3` PTSIP classification.
 
 VPMS verification PASS does not imply PTSIP `CONFORMANT`, and PTSIP `CONFORMANT` does not imply functional verification PASS.
 
@@ -431,6 +433,20 @@ in its Tool release note; advancing the PP contract does not rewrite that Tool h
 
 A new immutable revision is required only for a genuine normative change. Release workflow, test, planning, status, or documentation-only changes do not move `SPEC_REVISION` by themselves.
 
+## Tool 0.3.8a3 release identity
+
+Tool `0.3.8a3` is an emergency Context Plane migration-semantics patch over the published `0.3.8a2` repository-namespace release.
+
+```text
+Tool:             0.3.8a3
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    deterministic MEMORY.md -> Context Plane migration and projection repair
+```
+
+The canonical semantic write target is `.ptsip/context/source/context.source.json`. Generated `context.json`, `context.jsonl`, and `context.schema.json` are repaired from that source. Semantic ambiguity remains user-owned; deterministic projection repair is preauthorized for coding agents. Unlike Tool `0.3.8a2`, Tool `0.3.8a3` ships this implementation inside the Consumer Tool as `ptsip/context_plane.py`; a release build is invalid if that module or the `ptsip context` CLI surface is absent from the built wheel.
+
 ## Tool 0.3.8a2 release identity
 
 Tool `0.3.8a2` is a repository-namespace stabilization prerelease with a deliberately narrow compatibility goal.
@@ -482,8 +498,8 @@ Read-only inspection and Pilot operations remain read-only and do not create rep
 
 Repository tooling implementations may physically live under `tools/`, `scripts/`, `src/`, or another project-owned path. Their PTSIP-owned registration, policy bindings, task/operation contracts, indexes, and lifecycle state must not establish an alternative repository-local PTSIP control-plane root.
 
-Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a2` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
+Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a3` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
 
 ## Project status
 
-PTSIP remains experimental. Tool `0.3.8a2` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a2.md`](releasenote/tool/0.3.8a2.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).
+PTSIP remains experimental. Tool `0.3.8a3` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a3.md`](releasenote/tool/0.3.8a3.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/README.md

@@ -4,8 +4,8 @@
 
 # PTSIP — Primary Lifecycle Ownership and Responsibility Isolation Policy
 
-**Status:** Tool `0.3.8a2` repository-namespace stabilization prerelease — publication pending<br>
-**Tool/package version:** `0.3.8a2`<br>
+**Status:** Tool `0.3.8a3` Context Plane migration-semantics emergency prerelease — publication pending<br>
+**Tool/package version:** `0.3.8a3`<br>
 **Project Profile contract:** `pp.1.02`<br>
 **Specification family:** `0.3.7-draft`<br>
 **Bound immutable Specification revision:** `3c47816770d194ae42f98faedc911d980db0e62a`<br>
@@ -17,11 +17,11 @@ PTSIP is a project-defined architecture policy for separating project responsibi
 
 > **Purpose precedes reuse.** Classify a coherent responsibility by why it exists and which lifecycle owns it before optimizing for code sharing.
 
-Tool `0.3.8a2` is a repository-namespace stabilization prerelease built on the already-published `0.3.8a1` bridge and the same frozen Specification binding. It preserves the proposed-candidate bridge while establishing `.ptsip/` as the canonical repository-local ownership boundary for PTSIP-managed contracts, registries, configuration, task/operation metadata, and execution state. Canonical repository indexes use JSON. This release reserves Task and runtime namespaces but does not claim a completed generic Task Engine, Go runtime, or Tool `0.4.0` capability-recovery implementation.
+Tool `0.3.8a3` is an emergency corrective prerelease over the published `0.3.8a2` repository-namespace release. Tool `0.3.8a2` established `.ptsip/` and the provider-neutral Context Plane at repository level, but its Context Projection implementation remained under `developer/automation/` and therefore was not shipped in the installed Consumer Tool. Tool `0.3.8a3` closes that packaging and migration gap by shipping the canonical Context Plane implementation as `ptsip.context_plane`, exposing `ptsip context status|migrate|repair|check`, and binding release verification to the installed wheel. The Specification and Project Profile identities remain unchanged.
 
 ## Primary lifecycle ownership
 
-Canonical Tool `0.3.8a2` classifications remain exactly:
+Canonical Tool `0.3.8a3` classifications remain exactly:
 
 | Classification | Meaning |
 | --- | --- |
@@ -43,9 +43,9 @@ TOOLCHAIN
 NEUTRAL_CONTRACT
 ```
 
-Tool `0.3.8a2` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
+Tool `0.3.8a3` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
 
-Tool `0.3.8a2` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
+Tool `0.3.8a3` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
 
 ## Classification is not path or technology
 
@@ -66,7 +66,7 @@ Paths such as `tests/`, `tools/`, `deploy/`, `ops/`, or `.github/workflows/` are
 
 ## Responsibility Map v2
 
-Tool `0.3.8a2` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
+Tool `0.3.8a3` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
 
 ```text
 classification
@@ -195,12 +195,12 @@ Upgrade to the latest **published** release:
 python -m pip install --upgrade PTSIP
 ```
 
-Tool `0.3.8a2` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
+Tool `0.3.8a3` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
 
 After publication, install this prerelease explicitly with:
 
 ```powershell
-python -m pip install "PTSIP==0.3.8a2"
+python -m pip install "PTSIP==0.3.8a3"
 ```
 
 For source development on this release line:
@@ -223,6 +223,8 @@ ptsip clarify .
 ptsip gate .
 ptsip resolve --help
 ptsip conform .
+ptsip context status . --json
+ptsip context check . --json
 ```
 
 New project-owned profiles are selected through `.ptsip/profiles/index.json`; the catalog's `default_profile` resolves the active `*.ptsip.yaml` resource. Repository-root `ptsip.yaml` remains a compatibility/migration input, and an explicit `--profile` path still takes precedence.
@@ -231,7 +233,7 @@ New project-owned profiles are selected through `.ptsip/profiles/index.json`; th
 
 Repository evidence is not architecture authority. Candidate discovery, path names, templates, heuristics, and agent confidence can support review but cannot manufacture project intent.
 
-Canonical Tool `0.3.8a2` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
+Canonical Tool `0.3.8a3` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
 
 ```text
 classification
@@ -241,7 +243,7 @@ runtime_required
 executable
 ```
 
-The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a2` ownership authority.
+The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a3` ownership authority.
 
 Example dry-run:
 
@@ -306,7 +308,7 @@ PTSIP uses action-time synchronization rather than continuous background polling
 
 Artifact ownership is independent from producer ownership. A `DEVELOPMENT_TOOLING` or `DELIVERY` component may validly build a `PRODUCT` artifact, but the resulting artifact must still satisfy the Product package boundary.
 
-Tool `0.3.8a2` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
+Tool `0.3.8a3` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
 
 ## VPMS — Verification Purpose Management System
 
@@ -322,7 +324,7 @@ VPMS
 
 PTSIP classification and VPMS Verification Purpose remain separate axes. PTSIP core does not depend on VPMS. VPMS consumes only a narrow read-only projection of already-resolved PTSIP metadata.
 
-The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a2` PTSIP classification.
+The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a3` PTSIP classification.
 
 VPMS verification PASS does not imply PTSIP `CONFORMANT`, and PTSIP `CONFORMANT` does not imply functional verification PASS.
 
@@ -393,6 +395,20 @@ in its Tool release note; advancing the PP contract does not rewrite that Tool h
 
 A new immutable revision is required only for a genuine normative change. Release workflow, test, planning, status, or documentation-only changes do not move `SPEC_REVISION` by themselves.
 
+## Tool 0.3.8a3 release identity
+
+Tool `0.3.8a3` is an emergency Context Plane migration-semantics patch over the published `0.3.8a2` repository-namespace release.
+
+```text
+Tool:             0.3.8a3
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    deterministic MEMORY.md -> Context Plane migration and projection repair
+```
+
+The canonical semantic write target is `.ptsip/context/source/context.source.json`. Generated `context.json`, `context.jsonl`, and `context.schema.json` are repaired from that source. Semantic ambiguity remains user-owned; deterministic projection repair is preauthorized for coding agents. Unlike Tool `0.3.8a2`, Tool `0.3.8a3` ships this implementation inside the Consumer Tool as `ptsip/context_plane.py`; a release build is invalid if that module or the `ptsip context` CLI surface is absent from the built wheel.
+
 ## Tool 0.3.8a2 release identity
 
 Tool `0.3.8a2` is a repository-namespace stabilization prerelease with a deliberately narrow compatibility goal.
@@ -444,8 +460,8 @@ Read-only inspection and Pilot operations remain read-only and do not create rep
 
 Repository tooling implementations may physically live under `tools/`, `scripts/`, `src/`, or another project-owned path. Their PTSIP-owned registration, policy bindings, task/operation contracts, indexes, and lifecycle state must not establish an alternative repository-local PTSIP control-plane root.
 
-Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a2` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
+Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a3` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
 
 ## Project status
 
-PTSIP remains experimental. Tool `0.3.8a2` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a2.md`](releasenote/tool/0.3.8a2.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).
+PTSIP remains experimental. Tool `0.3.8a3` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a3.md`](releasenote/tool/0.3.8a3.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).

ptsip-0.3.8a3/docs/Support_policy/policy/SFP-0022.yaml

@@ -0,0 +1,53 @@
+schema_version: ptsip-support-feature-policy/v1
+policy_class: PTSIP_SUPPORT_FEATURE
+policy:
+  id: SFP-0022
+  title: Context Plane Migration and Deterministic Projection Repair
+  status: ACTIVE
+feature_contract:
+  shipped: true
+  runtime_surface:
+    - src/ptsip/context_plane.py
+    - src/ptsip/cli.py
+authority_contract:
+  authority_type: CONTEXT_PLANE_MIGRATION_REPAIR
+  schema_id: ptsip.context/migration-repair
+  schema_version: 1
+authority_semantics:
+  canonical_semantic_source: .ptsip/context/source/context.source.json
+  generated_projections:
+    - .ptsip/context/context.json
+    - .ptsip/context/context.jsonl
+    - .ptsip/context/context.schema.json
+  normal_direct_projection_edit: FORBIDDEN
+  deterministic_projection_repair:
+    coding_agent_authorization: PREAUTHORIZED
+    user_decision_required: false
+  semantic_source_creation_from_legacy_memory:
+    legacy_memory_read_scope: MIGRATION_ONLY
+    deterministic_conversion_authorization: PREAUTHORIZED
+    semantic_ambiguity: OWNER_DECISION_REQUIRED
+  existing_semantic_source_replacement:
+    authorization: USER_EXPLICIT
+    silent_agent_selection: FORBIDDEN
+  legacy_memory_deletion:
+    before_context_validation: FORBIDDEN
+    after_context_validation: PREAUTHORIZED
+    migration_failure_preserves_legacy_memory: true
+  emergency_direct_projection_repair:
+    authorization: USER_EXPLICIT
+    status: TEMPORARY_ONLY
+    release_while_active: FORBIDDEN
+    required_reconciliation:
+      - REGENERATE_FROM_CANONICAL_SOURCE
+      - CONTEXT_CHECK_PASS
+  release_gate:
+    context_check: REQUIRED
+    missing_projection: FAIL_CLOSED
+    projection_drift: FAIL_CLOSED
+    semantic_equivalence_failure: FAIL_CLOSED
+relations:
+  supersedes: []
+  amends: []
+  extends: []
+  depends_on: []

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/index.yaml

@@ -64,3 +64,6 @@ policies:
   - id: SFP-0021
     path: SFP-0021.yaml
     status: ACTIVE
+  - id: SFP-0022
+    path: SFP-0022.yaml
+    status: ACTIVE

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/registries/ptsip-support-authority-role-registry.yaml

@@ -368,6 +368,18 @@ policy_roles:
       - govern_specification_capabilities
       - require_explicit_specification_binding
       - separate_cross_contract_identity_axes
+  - policy_id: SFP-0022
+    projection_role: PROJECT_ARCHITECTURE_AUTHORITY
+    resolution_state: DECLARED
+    effects:
+      - constrain_machine_output_structure
+      - deny_unauthorized_semantic_inference
+      - fail_closed_on_invalid_state
+      - govern_migration_execution_authorization
+      - govern_migration_execution_state_machine
+      - require_deterministic_integrity_digest
+      - require_project_owner_decision
+      - separate_global_authority_from_local_projection
 invariants:
   registered_effect_token_is_project_authority_by_itself: false
   projection_role_is_current_eligibility_result_by_itself: false

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/registries/ptsip-support-authority-schema-registry.yaml

@@ -117,3 +117,8 @@ entries:
     schema_id: ptsip.governance/specification-binding-capability-registries
     schema_version: 1
     schema_definition: SFP_0021_V1
+  - policy_id: SFP-0022
+    authority_type: CONTEXT_PLANE_MIGRATION_REPAIR
+    schema_id: ptsip.context/migration-repair
+    schema_version: 1
+    schema_definition: SFP_0022_V1

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/registries/ptsip-support-authority-subject-registry.yaml

@@ -31,6 +31,7 @@ subject_identity_schemes:
       - SFP-0019
       - SFP-0020
       - SFP-0021
+      - SFP-0022
 repository_identity_schemes:
   GITHUB_REPOSITORY_ID:
     host_required: true

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/schemas/ptsip-support-authority-semantics.schema.json

@@ -581,6 +581,50 @@
         "historical_bridge_role": "MIGRATION_INTERPRETATION_ONLY",
         "unsupported_or_malformed_binding": "FAIL_CLOSED"
       }
+    },
+    "SFP_0022_V1": {
+      "const": {
+        "canonical_semantic_source": ".ptsip/context/source/context.source.json",
+        "generated_projections": [
+          ".ptsip/context/context.json",
+          ".ptsip/context/context.jsonl",
+          ".ptsip/context/context.schema.json"
+        ],
+        "normal_direct_projection_edit": "FORBIDDEN",
+        "deterministic_projection_repair": {
+          "coding_agent_authorization": "PREAUTHORIZED",
+          "user_decision_required": false
+        },
+        "semantic_source_creation_from_legacy_memory": {
+          "legacy_memory_read_scope": "MIGRATION_ONLY",
+          "deterministic_conversion_authorization": "PREAUTHORIZED",
+          "semantic_ambiguity": "OWNER_DECISION_REQUIRED"
+        },
+        "existing_semantic_source_replacement": {
+          "authorization": "USER_EXPLICIT",
+          "silent_agent_selection": "FORBIDDEN"
+        },
+        "legacy_memory_deletion": {
+          "before_context_validation": "FORBIDDEN",
+          "after_context_validation": "PREAUTHORIZED",
+          "migration_failure_preserves_legacy_memory": true
+        },
+        "emergency_direct_projection_repair": {
+          "authorization": "USER_EXPLICIT",
+          "status": "TEMPORARY_ONLY",
+          "release_while_active": "FORBIDDEN",
+          "required_reconciliation": [
+            "REGENERATE_FROM_CANONICAL_SOURCE",
+            "CONTEXT_CHECK_PASS"
+          ]
+        },
+        "release_gate": {
+          "context_check": "REQUIRED",
+          "missing_projection": "FAIL_CLOSED",
+          "projection_drift": "FAIL_CLOSED",
+          "semantic_equivalence_failure": "FAIL_CLOSED"
+        }
+      }
     }
   }
 }

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/docs/Support_policy/policy/schemas/ptsip-support-feature-policy-index.schema.json

@@ -17,8 +17,8 @@
     },
     "policies": {
       "type": "array",
-      "minItems": 21,
-      "maxItems": 21,
+      "minItems": 22,
+      "maxItems": 22,
       "uniqueItems": true,
       "items": {
         "type": "object",

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PTSIP"
-version = "0.3.8a2"
+version = "0.3.8a3"
 description = "Reference tooling for primary lifecycle ownership and responsibility isolation"
 readme = "README.md"
 requires-python = ">=3.11"

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/src/PTSIP.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PTSIP
-Version: 0.3.8a2
+Version: 0.3.8a3
 Summary: Reference tooling for primary lifecycle ownership and responsibility isolation
 Author: Kinirin
 Maintainer: Kinirin
@@ -42,8 +42,8 @@ Dynamic: license-file
 
 # PTSIP — Primary Lifecycle Ownership and Responsibility Isolation Policy
 
-**Status:** Tool `0.3.8a2` repository-namespace stabilization prerelease — publication pending<br>
-**Tool/package version:** `0.3.8a2`<br>
+**Status:** Tool `0.3.8a3` Context Plane migration-semantics emergency prerelease — publication pending<br>
+**Tool/package version:** `0.3.8a3`<br>
 **Project Profile contract:** `pp.1.02`<br>
 **Specification family:** `0.3.7-draft`<br>
 **Bound immutable Specification revision:** `3c47816770d194ae42f98faedc911d980db0e62a`<br>
@@ -55,11 +55,11 @@ PTSIP is a project-defined architecture policy for separating project responsibi
 
 > **Purpose precedes reuse.** Classify a coherent responsibility by why it exists and which lifecycle owns it before optimizing for code sharing.
 
-Tool `0.3.8a2` is a repository-namespace stabilization prerelease built on the already-published `0.3.8a1` bridge and the same frozen Specification binding. It preserves the proposed-candidate bridge while establishing `.ptsip/` as the canonical repository-local ownership boundary for PTSIP-managed contracts, registries, configuration, task/operation metadata, and execution state. Canonical repository indexes use JSON. This release reserves Task and runtime namespaces but does not claim a completed generic Task Engine, Go runtime, or Tool `0.4.0` capability-recovery implementation.
+Tool `0.3.8a3` is an emergency corrective prerelease over the published `0.3.8a2` repository-namespace release. Tool `0.3.8a2` established `.ptsip/` and the provider-neutral Context Plane at repository level, but its Context Projection implementation remained under `developer/automation/` and therefore was not shipped in the installed Consumer Tool. Tool `0.3.8a3` closes that packaging and migration gap by shipping the canonical Context Plane implementation as `ptsip.context_plane`, exposing `ptsip context status|migrate|repair|check`, and binding release verification to the installed wheel. The Specification and Project Profile identities remain unchanged.
 
 ## Primary lifecycle ownership
 
-Canonical Tool `0.3.8a2` classifications remain exactly:
+Canonical Tool `0.3.8a3` classifications remain exactly:
 
 | Classification | Meaning |
 | --- | --- |
@@ -81,9 +81,9 @@ TOOLCHAIN
 NEUTRAL_CONTRACT
 ```
 
-Tool `0.3.8a2` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
+Tool `0.3.8a3` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
 
-Tool `0.3.8a2` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
+Tool `0.3.8a3` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
 
 ## Classification is not path or technology
 
@@ -104,7 +104,7 @@ Paths such as `tests/`, `tools/`, `deploy/`, `ops/`, or `.github/workflows/` are
 
 ## Responsibility Map v2
 
-Tool `0.3.8a2` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
+Tool `0.3.8a3` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
 
 ```text
 classification
@@ -233,12 +233,12 @@ Upgrade to the latest **published** release:
 python -m pip install --upgrade PTSIP
 ```
 
-Tool `0.3.8a2` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
+Tool `0.3.8a3` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
 
 After publication, install this prerelease explicitly with:
 
 ```powershell
-python -m pip install "PTSIP==0.3.8a2"
+python -m pip install "PTSIP==0.3.8a3"
 ```
 
 For source development on this release line:
@@ -261,6 +261,8 @@ ptsip clarify .
 ptsip gate .
 ptsip resolve --help
 ptsip conform .
+ptsip context status . --json
+ptsip context check . --json
 ```
 
 New project-owned profiles are selected through `.ptsip/profiles/index.json`; the catalog's `default_profile` resolves the active `*.ptsip.yaml` resource. Repository-root `ptsip.yaml` remains a compatibility/migration input, and an explicit `--profile` path still takes precedence.
@@ -269,7 +271,7 @@ New project-owned profiles are selected through `.ptsip/profiles/index.json`; th
 
 Repository evidence is not architecture authority. Candidate discovery, path names, templates, heuristics, and agent confidence can support review but cannot manufacture project intent.
 
-Canonical Tool `0.3.8a2` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
+Canonical Tool `0.3.8a3` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
 
 ```text
 classification
@@ -279,7 +281,7 @@ runtime_required
 executable
 ```
 
-The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a2` ownership authority.
+The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a3` ownership authority.
 
 Example dry-run:
 
@@ -344,7 +346,7 @@ PTSIP uses action-time synchronization rather than continuous background polling
 
 Artifact ownership is independent from producer ownership. A `DEVELOPMENT_TOOLING` or `DELIVERY` component may validly build a `PRODUCT` artifact, but the resulting artifact must still satisfy the Product package boundary.
 
-Tool `0.3.8a2` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
+Tool `0.3.8a3` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
 
 ## VPMS — Verification Purpose Management System
 
@@ -360,7 +362,7 @@ VPMS
 
 PTSIP classification and VPMS Verification Purpose remain separate axes. PTSIP core does not depend on VPMS. VPMS consumes only a narrow read-only projection of already-resolved PTSIP metadata.
 
-The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a2` PTSIP classification.
+The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a3` PTSIP classification.
 
 VPMS verification PASS does not imply PTSIP `CONFORMANT`, and PTSIP `CONFORMANT` does not imply functional verification PASS.
 
@@ -431,6 +433,20 @@ in its Tool release note; advancing the PP contract does not rewrite that Tool h
 
 A new immutable revision is required only for a genuine normative change. Release workflow, test, planning, status, or documentation-only changes do not move `SPEC_REVISION` by themselves.
 
+## Tool 0.3.8a3 release identity
+
+Tool `0.3.8a3` is an emergency Context Plane migration-semantics patch over the published `0.3.8a2` repository-namespace release.
+
+```text
+Tool:             0.3.8a3
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    deterministic MEMORY.md -> Context Plane migration and projection repair
+```
+
+The canonical semantic write target is `.ptsip/context/source/context.source.json`. Generated `context.json`, `context.jsonl`, and `context.schema.json` are repaired from that source. Semantic ambiguity remains user-owned; deterministic projection repair is preauthorized for coding agents. Unlike Tool `0.3.8a2`, Tool `0.3.8a3` ships this implementation inside the Consumer Tool as `ptsip/context_plane.py`; a release build is invalid if that module or the `ptsip context` CLI surface is absent from the built wheel.
+
 ## Tool 0.3.8a2 release identity
 
 Tool `0.3.8a2` is a repository-namespace stabilization prerelease with a deliberately narrow compatibility goal.
@@ -482,8 +498,8 @@ Read-only inspection and Pilot operations remain read-only and do not create rep
 
 Repository tooling implementations may physically live under `tools/`, `scripts/`, `src/`, or another project-owned path. Their PTSIP-owned registration, policy bindings, task/operation contracts, indexes, and lifecycle state must not establish an alternative repository-local PTSIP control-plane root.
 
-Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a2` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
+Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a3` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
 
 ## Project status
 
-PTSIP remains experimental. Tool `0.3.8a2` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a2.md`](releasenote/tool/0.3.8a2.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).
+PTSIP remains experimental. Tool `0.3.8a3` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a3.md`](releasenote/tool/0.3.8a3.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).

{ptsip-0.3.8a2 → ptsip-0.3.8a3}/src/PTSIP.egg-info/SOURCES.txt

@@ -29,6 +29,7 @@ docs/Support_policy/policy/SFP-0018.yaml
 docs/Support_policy/policy/SFP-0019.yaml
 docs/Support_policy/policy/SFP-0020.yaml
 docs/Support_policy/policy/SFP-0021.yaml
+docs/Support_policy/policy/SFP-0022.yaml
 docs/Support_policy/policy/index.yaml
 docs/Support_policy/policy/registries/ptsip-support-authority-role-registry.yaml
 docs/Support_policy/policy/registries/ptsip-support-authority-schema-registry.yaml
@@ -167,6 +168,7 @@ src/ptsip/conformance.py
 src/ptsip/conformance_audit.py
 src/ptsip/conformance_engine.py
 src/ptsip/constants.py
+src/ptsip/context_plane.py
 src/ptsip/dependency_analysis.py
 src/ptsip/dependency_cache.py
 src/ptsip/dependency_reconciliation.py