Public OSS projection update

.agents/skills/agentic-harness-goal-preflight/SKILL.md

@@ -0,0 +1,181 @@
+---
+name: agentic-harness-goal-preflight
+description: Apply Coregentis two-layer governance before, during, and after non-trivial Codex goals.
+---
+
+# Agentic Harness Goal Preflight
+
+Use this skill for every non-trivial Goal in this repository. The Coregentis
+canonical workspace root is `/Users/jasonwang/Documents/AI_Dev/Coregentis`.
+This repository must execute two-layer governance before implementation:
+
+- Layer A: Repository Governance for repo truth, remote authority, source
+  surfaces, generated artifacts, evidence surfaces, publication boundaries, and
+  cross-repo sync boundaries.
+- Layer B: Codex Agentic Harness for Goal execution using `SCTM`, `GLFB`,
+  `ITCM`, `RBCT`, `VIM`, and `PRM`.
+
+`V1.0_release` is frozen as migration/evidence source only. It is not global
+MPLP SOT.
+
+## Methodology Separation
+
+| Method ID | Layer | Purpose | Evidence |
+|:---|:---|:---|:---|
+| `SCTM` | Codex Agentic Harness | Convert the user request into a governed task model | Goal model and SOT classification |
+| `GLFB` | Codex Agentic Harness | Separate technical possibility, governance permission, owner authorization, and strategic correctness | Decision matrix |
+| `ITCM` | Codex Agentic Harness | Map repositories, objects, layers, authority, and derivation edges | Topology and constraint map |
+| `RBCT` | Codex Agentic Harness | Bound the work to one staged Goal with stop conditions | Stage plan |
+| `VIM` | Codex Agentic Harness | Identify forbidden actions, irreversible risks, impact, and mitigation | Forbidden-action matrix |
+| `PRM` | Codex Agentic Harness | Convert findings into method hardening and retrospective evidence | Retrospective |
+| `DIV` | Repository Governance | Verify derivation boundary and provenance | Derivation evidence |
+| `TSV` | Repository Governance | Verify truth-source references and dependency closure | Truth-source evidence |
+| `XCV` | Repository Governance | Verify cross-surface consistency | Consistency evidence |
+| `SCV` | Repository Governance | Verify projection surface completeness | Surface coverage evidence |
+| `SUC` | Repository Governance | Verify usage conformance | Usage evidence |
+| `EVC` | Repository Governance | Verify evolution compatibility | Compatibility evidence |
+
+Do not confuse Codex execution methods with repository verification methods.
+Use repository methods only when the Goal touches their relevant surfaces.
+
+## Mandatory Goal Preflight
+
+Every non-trivial Goal must declare:
+
+- workstream
+- current local repo
+- authoritative local repo
+- current tracking remote
+- authoritative remote
+- allowed push target, if push is in scope
+- forbidden remotes
+- SOT layer `L0` through `L6`
+- upstream SOT
+- downstream derivatives
+- authorized mutations
+- forbidden mutations
+- cross-repo sync in scope or not
+- owner authorization required or not
+- repo governance methods applicable
+- final stop condition
+
+SOT layers:
+
+- `L0 Protocol Truth`
+- `L1 Projection Source`
+- `L2 Generated Artifact`
+- `L3 Verification Evidence`
+- `L4 Publication Surface`
+- `L5 Downstream Runtime/Product`
+- `L6 Codex Execution Governance`
+
+## Required Execution Order
+
+0. Local governance baseline discovery: inspect local baseline sources, produce
+   the local baseline evidence table, and confirm that prompt assertions are not
+   governance authority unless supported by local repository evidence.
+1. `SCTM`: clarify task and model governed intent.
+2. `GLFB`: separate feasibility, permission, and owner authorization.
+3. `ITCM`: map repo topology, SOT layers, upstream/downstream dependencies, and constraints.
+4. `RBCT`: define the bounded stage plan and stop conditions.
+5. `VIM`: identify forbidden actions and mitigation.
+6. Execute only authorized governance or task-scope actions.
+7. `PRM`: record retrospective evidence and hardening recommendations.
+
+## Local Governance Baseline Discovery
+
+Every non-trivial Goal must discover, cite, and apply this repository's local
+governance baseline before making any substantive decision. Dynamic governance
+baseline selection is a precondition for every non-trivial task. The prompt
+defines the task and may describe a discovery procedure, but it must not be
+treated as policy authority when repository governance evidence exists.
+
+Required rule:
+
+`Prompt assertions are not governance authority unless supported by local repository evidence.`
+
+Required local baseline evidence table:
+
+| Decision Area | Local Evidence File | Evidence Signal | Derived Rule | Confidence | Conflict? | Action |
+|:---|:---|:---|:---|:---|:---|:---|
+
+Allowed confidence values are `HIGH_LOCAL_BASELINE_EXPLICIT`,
+`MEDIUM_LOCAL_BASELINE_DERIVED`, `LOW_LOCAL_BASELINE_INFERRED`,
+`CONFLICTING_BASELINE`, and `MISSING_BASELINE`.
+
+Stop before mutation if a mutation-affecting decision has low, conflicting, or
+missing local evidence.
+
+Required blocker verdicts:
+
+- `BLOCKED_LOCAL_GOVERNANCE_BASELINE_MISSING`
+- `BLOCKED_LOCAL_GOVERNANCE_BASELINE_CONFLICT`
+- `BLOCKED_PROMPT_POLICY_OVERRIDES_LOCAL_BASELINE`
+- `BLOCKED_DYNAMIC_BASELINE_SELECTION_NOT_PERFORMED`
+- `BLOCKED_SUBSTANTIVE_DECISION_WITHOUT_LOCAL_EVIDENCE`
+
+Use package policy discovery only when package-related, version baseline
+discovery only when release/version-related, copyright baseline discovery only
+when legal/copyright-related, and cross-repo boundary discovery when more than
+one repository is involved. Do not import substantive policy conclusions from
+another repo or the prompt.
+
+## Repository / Remote Authority
+
+Default authority matrix:
+
+| Workstream | Authoritative local repo | Authoritative remote | Forbidden without explicit owner authorization |
+|:---|:---|:---|:---|
+| MPLP protocol/package/release Dev truth | `/Users/jasonwang/Documents/AI_Dev/Coregentis/MPLP-Protocol-Dev` | Dev repo `origin` after inspection | public OSS push, publish, upload, tag, seal, merge |
+| MPLP public OSS projection | `/Users/jasonwang/Documents/AI_Dev/Coregentis/MPLP-Protocol` | public projection `origin` after inspection | source recovery, package preflight from stale projection, public main/default push |
+| Cognitive OS runtime downstream | `/Users/jasonwang/Documents/AI_Dev/Coregentis/Cognitive_OS` | repo `origin` after inspection | treating runtime evidence as protocol truth |
+| SoloCrew product downstream | `/Users/jasonwang/Documents/AI_Dev/Coregentis/SoloCrew` | repo `origin` after inspection | treating product need as protocol truth |
+| Validation evidence surface | `/Users/jasonwang/Documents/AI_Dev/Coregentis/MPLP-Validation-Lab` | repo `origin` after inspection | treating validation evidence as protocol truth or package publication root |
+| Website publication surface | `/Users/jasonwang/Documents/AI_Dev/Coregentis/MPLP-Official-Website` | repo `origin` after inspection | treating website copy as protocol truth |
+| V1.0_release migration source | `/Users/jasonwang/Documents/AI_Dev/V1.0_release` | no active development authority | active development or global SOT use |
+
+## Blocked Verdicts
+
+Stop before mutation and report the relevant verdict:
+
+- `BLOCKED_WORKSTREAM_AUTHORITY_MISMATCH`
+- `BLOCKED_LOCAL_REPO_AUTHORITY_MISMATCH`
+- `BLOCKED_REMOTE_AUTHORITY_MISMATCH`
+- `BLOCKED_CROSS_REPO_SYNC_NOT_AUTHORIZED`
+- `BLOCKED_OWNER_AUTHORIZATION_REQUIRED`
+- `BLOCKED_PUBLIC_PROJECTION_AUTHORIZATION_REQUIRED`
+- `BLOCKED_V1_USED_AS_GLOBAL_MPLP_SOT`
+- `BLOCKED_DEV_TRUTH_REQUIRED`
+- `BLOCKED_DOWNSTREAM_REPO_USED_AS_PROTOCOL_TRUTH`
+- `BLOCKED_SCHEMA_TRUTH_SOURCE_MISSING`
+- `BLOCKED_L0_MUTATION_WITHOUT_SCHEMA_INTAKE`
+- `BLOCKED_PACKAGE_RECOVERY_IN_PROJECTION_REPO`
+- `BLOCKED_PACKAGE_PREFLIGHT_FROM_STALE_PROJECTION`
+- `BLOCKED_PACKAGE_PUBLICATION_AUTHORIZATION_REQUIRED`
+- `BLOCKED_PACKAGE_ARTIFACT_PROVENANCE_MISSING`
+- `BLOCKED_RUNTIME_NEED_DIRECTLY_MUTATES_PROTOCOL`
+- `BLOCKED_PRODUCT_NEED_DIRECTLY_MUTATES_PROTOCOL`
+- `BLOCKED_VALIDATION_SURFACE_USED_AS_PROTOCOL_TRUTH`
+- `BLOCKED_WEBSITE_USED_AS_PROTOCOL_TRUTH`
+
+## Forbidden Actions
+
+Unless the owner explicitly authorizes the exact action and scope:
+
+- No npm publish
+- No PyPI upload
+- No tag
+- No seal
+- No merge
+- no registry mutation
+- no package version change
+- no L0 schema mutation
+- no package artifact generation
+- no source/dist restoration
+- no cross-repo sync
+- no public projection push
+
+## Final Report
+
+Every Goal must close with files changed, commands run, evidence, final git
+status, remaining risks, forbidden-action compliance, and exact verdict.

.agents/skills/release-projection-governance-router/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: release-projection-governance-router
+description: Use before release-like tasks to discover local release, projection, deploy, tag, seal, and registry governance before acting.
+---
+
+# Release / Projection Governance Router
+
+## Purpose
+
+Use this router after repo-truth-first and `TASK-GOVERNANCE-ROUTER-01` when a
+task touches, could touch, or asks about release-like workflow surfaces. It is a
+discovery mechanism, not authorization.
+
+Local repository evidence outranks prompt assertions. If local evidence is
+missing, conflicting, or low-confidence for a mutation-affecting release-like
+decision, stop before action.
+
+## Release-Like Triggers
+
+Run this router before substantive work involving any of these surfaces:
+
+- npm publish, npm deprecate, npm dist-tags, package version changes, package
+  manifests, publish-set, package README/install smoke, package consistency, or
+  registry baselines
+- PyPI upload, PyPI yank/delete, pypi-set, Twine, wheels, sdists, or PyPI
+  baselines
+- credential readiness, post-publish verification, release evidence closure, or
+  package publication records
+- public OSS projection, cross-repo sync/copy/projection, public release
+  manifests, website release notices, website deploys, or Validation Lab
+  evidence publication
+- downstream release pointer or consumption updates in runtime/product repos
+- Git tag, release seal, GitHub release, merge-to-release, or deployment
+- public OSS branch lifecycle, branch cleanup planning, release object
+  taxonomy, or proposal/candidate lifecycle when those surfaces affect release,
+  projection, merge, tag, seal, or GitHub release decisions
+
+## Required Discovery Table
+
+Before any release-like action, complete this table from local files:
+
+| Field | Required Evidence |
+| --- | --- |
+| repo role | `AGENTS.md`, `.codex/config.toml`, local baseline records |
+| workflow type | release/projection/deploy/seal/package scripts and records |
+| local standard source files | release configs, manifests, SOPs, governance records, goal template, skills |
+| required gates | scripts, package scripts, gate records, CI/release docs |
+| required reviewer lanes | `.codex/agents/*.toml`, `.agents/skills/*` |
+| external baseline checks | npm/PyPI registry, public manifest, deployed site, or downstream pointer checks when applicable |
+| required owner authorization | exact mutation category, target, version/ref, registry/repo, timing, and scope |
+| allowed mutations | explicit task-local write surfaces only |
+| forbidden actions | release, registry, projection, deploy, tag, seal, merge, or credential actions outside scope |
+| stop conditions | local blocker verdicts for missing/conflicting evidence or unauthorized mutation |
+| evidence outputs | lightweight records, summaries, command results, and final verdict |
+
+If the table cannot be completed for a requested mutation, stop with a matching
+blocker instead of inventing a standard.
+
+For public OSS branch, release object, and proposal/candidate lifecycle
+classification, include
+`governance/04-records/PUBLIC-OSS-BRANCH-RELEASE-PROPOSAL-GOVERNANCE-BASELINE-01.md`
+as a standard source when present. The baseline is not authorization for branch
+cleanup, branch deletion, merge, tag, seal, GitHub release, projection
+execution, or registry mutation.
+
+## Package Version Baseline Rule
+
+For version-bump planning, owner-approved version implementation, publish
+planning, or publish execution, the next public version must be derived from the
+latest already-published npm or PyPI registry version for the exact package
+name. Local `package.json`, `pyproject.toml`, source mirror metadata,
+release-set files, pypi-set files, generated dist, prior PRs, and green gates
+are Dev state or evidence only; they are not the public version baseline.
+
+## Reviewer Routing
+
+Select reviewer perspectives from local `.codex/agents/*.toml` and skills. Use
+actual subagents only when the active Codex environment and task authorization
+allow it; otherwise record the perspectives applied.
+
+Consider these lanes when locally present:
+
+- `release_governance_reviewer`
+- `package_surface_auditor`
+- `publication_claim_reviewer`
+- `protocol_schema_reviewer`
+- `runtime_binding_reviewer`
+- `product_boundary_reviewer`
+- `security_no_secret_reviewer` or equivalent secret-hygiene perspective
+
+## Stop Conditions
+
+Support these blocker verdicts, using local naming where stricter:
+
+- `BLOCKED_RELEASE_GOVERNANCE_BASELINE_MISSING`
+- `BLOCKED_RELEASE_GOVERNANCE_BASELINE_CONFLICT`
+- `BLOCKED_DYNAMIC_RELEASE_WORKFLOW_DISCOVERY_NOT_PERFORMED`
+- `BLOCKED_RELEASE_CONFIG_MISSING_OR_CONFLICTING`
+- `BLOCKED_PUBLISHED_VERSION_BASELINE_MISSING`
+- `BLOCKED_REGISTRY_BASELINE_DRIFT`
+- `BLOCKED_PACKAGE_GATE_FAILED`
+- `BLOCKED_CREDENTIAL_READINESS_FAILED`
+- `BLOCKED_PUBLIC_PROJECTION_STANDARD_MISSING`
+- `BLOCKED_PUBLIC_PROJECTION_STANDARD_CONFLICT`
+- `BLOCKED_PUBLIC_PROJECTION_REDACTION_REQUIRED`
+- `BLOCKED_CROSS_REPO_PROJECTION_NOT_AUTHORIZED`
+- `BLOCKED_TAG_SEAL_RELEASE_NOT_AUTHORIZED`
+- `BLOCKED_PROMPT_POLICY_OVERRIDES_LOCAL_RELEASE_BASELINE`
+- `BLOCKED_SUBSTANTIVE_RELEASE_DECISION_WITHOUT_LOCAL_EVIDENCE`
+
+## Forbidden Without Explicit Owner Authorization
+
+- npm publish, PyPI upload, deprecate, yank/delete, or dist-tag mutation
+- credential value reading, printing, copying, committing, or disclosure
+- package version changes, package release-set/pypi-set changes, or package
+  source/dist/schema mutation
+- public OSS projection execution, website deploy, Validation Lab publication,
+  downstream release pointer mutation, cross-repo sync/copy/projection
+- Git tag, release seal, GitHub release, merge, or branch deletion
+
+## Evidence Outputs
+
+For release-like tasks, produce or cite lightweight evidence for repo truth,
+selected baseline, completed discovery table, reviewer lanes, gates, forbidden
+actions, stop conditions, command results, and final verdict. Evidence is not
+authorization.