v1423

v1423 provides owner-managed repository contracts, deterministic stabilization reports, the shared Core/Cortex release conductor, and the Save, Preview, Publish workflow for projects governed by v14.23 Cortex, made by Spark Line.

npx --yes [email protected] contract check
npx --yes [email protected] repo status
npx --yes [email protected] repo start --branch feature/example

The three user actions are:

• Save — commit and push explicit task-owned files with no setup, build, test, or deploy work.
• Preview — run fast review checks, integrate through linkline, and produce a previewable immutable deployment.
• Publish — run the complete verification profile against that unchanged candidate before promoting it to production.

Example commands:

v1423 repo save --message "Update homepage" --path src/pages/index.astro --cortex-run <run-id>
v1423 repo preview --cortex-run <run-id>
v1423 repo publish --cortex-run <run-id>

The managed adapter supplies the current run ID when it executes these commands; the owner does not approve each underlying Git, pull-request, or deployment call. Each physical external sub-action still asks the authenticated loopback v14.23 Cortex authority for the exact admitted run, first-party tool, target digest, parameter digest, and unique action ID immediately before execution. A denied or unavailable authority leaves that external action untouched. PreToolUse remains early feedback only and never grants executor authority.

repo save --wip remains accepted but is deprecated; every Save is non-publishable until Preview and Publish assurance succeeds. Remote branch, tree, lockfile, toolchain, configuration, and deployment drift invalidate stale receipts. Production must be an ancestor of staging.

Contract v15 remains the v14.23 Core foundation contract. Cortex does not rewrite it: handshake schema 2, the three managed project files, exact skill discovery, approved Memory Map receipts, scoped review semantics, and owner-managed status remain compatible. Package 1.5.4 carries the Cortex successor release profile and quality-evidence runtime while contracts 1 through 15 remain targetable.

The selected Cortex successor profile is workspace migration ceiling 14, skill protocol 1, Cortex protocol 1, and adapter protocol 1. The deployed and final [email protected] bytes remain immutable historical evidence; after migration 14 they are not a manifest-ready release fallback. The browser app remains compatible outside the activation pins. The successor is a candidate until an exact final manifest is owner-approved and the conditional activating to active transaction completes with manifest-bound readiness probes and an activation receipt. Cortex is the sole forward active identity; historical Core release artifacts and [email protected] evidence remain immutable provenance.

v1423 release plan --plan core/release/v14.23-cortex.plan.json --source-root /clean/context --state-file /evidence/cortex.state.json --evidence-root /evidence
v1423 release apply --plan core/release/v14.23-cortex.plan.json --source-root /clean/context --state-file /evidence/cortex.state.json --evidence-root /evidence
v1423 release apply --plan core/release/v14.23-cortex.plan.json --manifest /evidence/v14.23-cortex.final.json --source-root /clean/context --state-file /evidence/cortex.state.json --evidence-root /evidence
v1423 release status --plan core/release/v14.23-cortex.plan.json --source-root /clean/context --state-file /evidence/cortex.state.json --evidence-root /evidence
v1423 fleet contract-rollout --registry fleet.json --mode plan
v1423 stabilize --repo /absolute/project --private-context /absolute/reviewed-context.md
npm run cortex:service-actors
npm run cortex:service-actors -- plan --remote

The contract updater remains bounded to:

• the marker-delimited v1423 section in AGENTS.md;
• approved v1423 fields in v1423.project.json;
• mcpServers.v1423 in .mcp.json.

The canonical release interface is the two-token release plan|apply|status form. Legacy release:plan, release:apply, and release:status remain compatibility aliases, and historical schema-v1 plan reads/defaults remain unchanged. Schema v2 supports both immutable historical Core and current Cortex release profiles. Each profile separates a six-phase operational plan, an external completion receipt, a lean immutable final manifest, an immutable activation recovery record, and an activation receipt. Every executable check has a concrete evidence-verification command and independently resumable phase/check state. Missing evidence remains pending; corrupt state, failed evidence, changed approval inputs, and incomplete receipts fail closed. A fully verified final manifest reaches ready-to-advertise; only the conditional activating to complete pointer flow makes it active. stabilize reads thread, ship, release-experience, and explicit private-context evidence and returns proposals only; it never writes or promotes canon.

Before private Cortex service evidence is accepted, the exact authenticated subject and runtime, evaluation, release, or system role must have an active workspace-scoped cortex_trusted_service_actors registration, and the resolver must recognize the service-only assignment bypass. The registration is an evidence-provenance gate, not a tool, review, delivery, or activation grant.

The app/bridge binding is source-cycle-free: generate it from the reviewed central profile and exact app module bytes, copy the generated binding and build manifest into the app, Save that app commit, then pin the saved app SHA in the external final manifest and obtain owner approval. The binding contains no repository SHA, release ID, or candidate/final-manifest digest, and its generated files are excluded from the hashed module list.

Contracts v1 through v14 remain explicitly targetable and byte-for-byte preserved. Contract sync itself never commits, pushes, merges, or deploys.