docs: operationalize Coven Automations v1 tracker roadmap and drift check (coven#859) - #3
Open
CompleteDotTech wants to merge 3 commits into
Conversation
…854) (OpenCoven#861) Adds one dated status/decision record for issue OpenCoven#854 in docs/superpowers/plans/. Independently verified against main @ 1364cec (2026-08-30): the coven#816 foundation series (PR OpenCoven#846, PR OpenCoven#847, parts 6-8 commits) landed the durable local scheduler core - definitions, SQLite definition/occurrence/run records with unique occurrence fencing, RRULE planning, bounded leases with expiry recovery, latest-only misfire / overlap refusal, the 60s daemon tick with scheduled dispatch, shared launch path, health and run history, non-destructive paused legacy import, and coven.automations.* control actions. Records what is still absent for v1 (versioned protocol schemas, authority/receipt binding, deterministic-time contract, SDK surface, conformance/chaos/SLO gates, live Beads mutation), the gate-by-gate verdict, and the critical path. The program issue remains open; this record closes no issue. Refs OpenCoven#854. Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com>
…oven#815) (OpenCoven#871) * docs: plan cryptographic fresh-user and biometric assurance proofs (coven#815) Specify COVEN-ASSURANCE/1, an independently verifiable step-up proof so request authentication can satisfy FreshUserVerification/FreshBiometric grant requirements without trusting client-asserted assurance levels. The plan defines: possession/step-up key separation; binding the optional step-up authorization key and its declared assurance class into the pairing-v2 transcript; a separate authorization-key store; canonical proof bytes over device, grant, revocation epoch, exact request or DeviceActionIntent digest, server-issued single-use challenge, window, and requested assurance; server-side effective assurance computed as min(claimed, class ceiling) and passed to DeviceGrant::authorize; fail-closed possession-only degradation; rotation/revocation semantics; iOS/Android platform mapping; a self-verifying synthetic golden vector; and TypeScript/JSON Schema for implementers. Every claim cites the current mobile_memory code path it builds on. No code changes: this is the design artifact the issue asks for. Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com> * docs(mobile): specify COVEN-ASSURANCE/1 step-up assurance proofs Add docs/design/mobile-assurance-step-up-v1.md, the plan and implementation contract for issue OpenCoven#815: a separately enrolled, platform-policy-protected step-up authorization key, bound into the pairing-v2 transcript before grant issuance, whose fresh signatures over canonical COVEN-ASSURANCE/1 bytes (device, grant, revocation epoch, exact request or DeviceActionIntent digest, single-use server challenge, validity window, requested assurance) are the only way to raise assurance above possession. The server verifies the signature, computes effective assurance itself, and passes it to DeviceGrant::authorize; absent/invalid/expired/replayed proofs fail closed. Covers storage separate from the possession key, replay protection independent of request nonces, rotation/revocation semantics, iOS/Android key-policy mapping, a security-invariant mapping, TypeScript types + JSON Schema, and a portable golden vector. Design artifact only; no behavior change. Refs OpenCoven#815 Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com> --------- Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com>
…heck (coven#859) Establish the GitHub-side half of the OpenCoven#859 operational delivery graph: - docs/roadmaps/coven-automations-v1.md: program roadmap with canonical tracker roles, sync metadata, P0/P1/P2 policy, generated outcome-mapping table, dependency graph, release gates, active blockers, and drift detection usage. The mapping table block is generated by docs/roadmaps/drift-check.mjs --render and verified on every run. - docs/roadmaps/coven-automations-v1.mapping.json: machine-readable one-to-one Bead <-> GitHub mapping for OpenCoven#854, OpenCoven#816, OpenCoven#855, OpenCoven#856, OpenCoven#857, and OpenCoven#858, with explicit dependencies, acceptance gates, dispositions, and evidence links. Bead IDs stay null (warn-level W010) until provisioning lands through OpenCoven/coven-cave#5220 per the operational correction on OpenCoven#859; no competing Beads store is created in this repository. - docs/roadmaps/drift-check.mjs: credential-free, offline drift check covering state, priority, parent/dependency, evidence, generated-mirror, duplicate/missing mapping, cycle, and sensitive-payload drift classes, with --beads-export cross-checking and --selftest proving detection. - docs/superpowers/plans/2026-08-30-issue-859-coven-automations-v1-...md: dated status/decision record: what exists on main (automations series landed 2026-08-28 via PRs OpenCoven#846/OpenCoven#847), pre-change integrity report, decisions D1-D7, verdict against the OpenCoven#859 acceptance criteria, remaining work, critical path, and the initial evidence packet. Refs OpenCoven#859 Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com> fix: keep automation tracker docs scanner-safe Signed-off-by: Timothy Wayne Gregg <5861166+CompleteDotTech@users.noreply.github.com>
CompleteDotTech
force-pushed
the
agent/issue-859-p0-control-operationalize-coven-automations-v1
branch
from
August 30, 2026 16:53
83ba34a to
91a005d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cave(OpenCoven/coven-cave),.beads/issues.jsonlthere is a public-scrubbed review export, and no competing Beads store is initialized in OpenCoven/coven. Bead provisioning itself is delegated to P0: Seed Coven Automations v1 into Cave’s canonical Beads/Dolt execution graph OpenCoven/coven-cave#5220; bead IDs staynull(warn-levelW010) in the mapping until #5220 declares them.Files changed (4 files, +1318)
docs/roadmaps/coven-automations-v1.md— roadmap artifact: canonical tracker roles (Beads / GitHub / Coven runtime), sync metadata (last sync, source branch, writer designation), P0/P1/P2 policy, generated outcome-mapping table, dependency graph, release gates, active blockers, drift-check usage; carries a generated-content warning and does not duplicate mutable run status.docs/roadmaps/coven-automations-v1.mapping.json— machine-readable one-to-one mapping for Program: Coven Automations v1 — reliable, identity-bound familiar routines OpenCoven/coven#854, Native familiar automations: replace harness-owned schedules with durable Coven routines OpenCoven/coven#816, P0: Specify coven.automations.v1 schemas, state machines, idempotency, and changefeed OpenCoven/coven#855, P0: Harden automation time, retries, cancellation, fencing, and crash recovery OpenCoven/coven#856, P0: Bind automation runs to principal authority, familiar revisions, capabilities, approvals, and receipts OpenCoven/coven#857, P0: Build automations conformance, chaos, SLO, and operator diagnostics OpenCoven/coven#858: explicitdepends_onedges matching P0 control: Operationalize Coven Automations v1 through Cave’s canonical Beads graph and GitHub mirrors OpenCoven/coven#859's minimum graph, acceptance gates, dispositions, evidence links, cross-repository child policy, and P2 exclusions.docs/roadmaps/drift-check.mjs— offline, dependency-free drift check (no network, no credentials): mapping invariants (duplicate/missing mapping, unknown deps, cycles, priority validity, P0 owner/gate/disposition, completed-work-without-evidence), generated-mirror contract enforcement (the roadmap table block is regenerated by--renderand verified on every run), optional--beads-export <issues.jsonl>cross-check (state/priority/surface:sharedlabel/1:1 linkage), sensitive-payload scan of tracker output, and--selftestproving every detection class with fixtures. Severity policy:errorfails CI;warning(pending provisioning) does not, keeping CI honest without staying red on work owned by another repository.docs/superpowers/plans/2026-08-30-issue-859-coven-automations-v1-tracker-operationalization.md— dated status/decision record: what exists onmaintoday (automations series landed 2026-08-28 via PRs feat(automations): routine definitions and control actions (coven#816, part 1) OpenCoven/coven#846/feat(automations): non-destructive legacy Codex import (coven#816, part 5) OpenCoven/coven#847, commits882fc83…1de50a8; no Beads store in this repo), pre-change integrity report (including the pre-existing push-onlyClassify changesCI failure on the base SHA), decisions D1–D7, criterion-by-criterion verdict, remaining work, critical path, and the initial evidence packet.Issue
Refs OpenCoven#859.
Deliberately not
Closes: the issue's own completion semantics keep OpenCoven#816 open until its evidence checklist is done, and OpenCoven#859 spans bead provisioning in OpenCoven/coven-cave#5220 (outside this repository). Closing on merge would close work that is only partially established; per OpenCoven#859, a GitHub issue is not closed merely because partial implementation landed.Test plan
Checked = ran locally in this checkout (node v24.16.0, no Rust toolchain, no python3):
node docs/roadmaps/drift-check.mjs --selftest— all 11 drift fixtures and 6 sensitive-payload rules detected (exit 0)node docs/roadmaps/drift-check.mjs— 0 errors; 6 ×W010pending-provisioning warnings, exit 0node docs/roadmaps/drift-check.mjs --beads-export .beads/issues.jsonlrun against theOpenCoven/coven-cavecheckout export — 0 errors; confirms zero Automations v1 beads exist and no sensitive payloads in the exportnode docs/roadmaps/drift-check.mjs --render— regenerated block is byte-identical to the committed one (idempotent)node --check docs/roadmaps/drift-check.mjs; JSON parse of the mapping filescripts/check-secrets.py/scripts/check-coven-privacy.py(python3 is unavailable locally) — cleanpython3 scripts/check-secrets.py+python3 scripts/check-coven-privacy.py --range— deferred to CI (policy-guard runs them on this PR)cargo fmt --check/cargo clippy/cargo test— deferred to CI; not applicable locally (no Rust toolchain) and not exercised by a docs-only diff (CI classification keeps Rust jobs skipped)Risk and Rollback
docs/); no code, no workflow changes, no tracker state mutated (bead state untouched; provisioning explicitly delegated to P0: Seed Coven Automations v1 into Cave’s canonical Beads/Dolt execution graph OpenCoven/coven-cave#5220).Agent Handoff
agent/issue-859-p0-control-operationalize-coven-automations-v1, based on upstreammainat1364cec; DCO signed-off.surface:sharedbeads via P0: Seed Coven Automations v1 into Cave’s canonical Beads/Dolt execution graph OpenCoven/coven-cave#5220, then set real bead IDs in the mapping (one-line reviewed change;W010clears, missing-mapping drift escalates toerror); (2) wirenode docs/roadmaps/drift-check.mjsinto relevant PR CI and the weekly rollup cadence; (3) fill the Native familiar automations: replace harness-owned schedules with durable Coven routines OpenCoven/coven#816 evidence checklist; (4) map cross-repository child outcomes one-to-one as they are created.bd/doltbinary) — bead reuse-check against live state is owned by #5220; thecoven claimregistry could not be used (no Rust toolchain to build the CLI) — REST deconfliction (no open PR or branch for P0 control: Operationalize Coven Automations v1 through Cave’s canonical Beads graph and GitHub mirrors OpenCoven/coven#859) plus a dedicated clone/branch covers the anti-duplication intent.CI note (checkless repository, draft→ready provenance)
CompleteDotTech/coven: the repository has never run a GitHub Actions workflow (0 total workflow runs, confirmed 2026-08-30 via the Actions API) and the head SHA83ba34a8a8d368d408c6637a424a0dfa4c8e0ca7reportscheck-runs total_count: 0. Per the draft-until-green contract for a checkless repository, there is no CI verdict to report; upstreamOpenCoven/covenchecks (policy-guard: secret scan, privacy guard; docs-only classification skips Rust jobs) will run when this branch is re-targeted upstream.gh pr create --repo OpenCoven/coven ..., 2026-08-30T15:24Z) failed withGraphQL: Resource not accessible by personal access token (createPullRequest); this fork PR is the working CI vehicle.ready_for_reviewevent was recorded at 2026-08-30T15:26:16Z by actorCompleteDotTech— the shared token identity used by concurrent sweeps — before any check could report. This session did not merge the PR and did not use GraphQL to change draft state; the REST API cannot convert a PR back to draft. End state (ready, unmerged) matches the checkless-repo contract outcome.