Repository navigation
docs(dag): defensive publication — ordered independent hard gates, non-compensatory evaluation, critical-failure cap - #268
Conversation
…s, non-compensatory evaluation, critical-failure cap Design disclosure placing the DAG-2026 multi-gate design on the public record as prior art. Symbolic only: HG-01..HG-07 predicates from CR-013 §2.3 with threshold names, never values. States plainly that no gate, registry, cap or typology code exists; only the verdict schema (0.84.1+) is public, with an empty reason-code seed and the flag off. Private-first. Not for public posting until Research approves and the owner OKs the GitHub post and arXiv submission. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 3266ad8470966bbc3fb4aa96776b6084384a5e03)
…rmed) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 8e65b4f1732b002b868b35628e75bf00931dc2ef)
|
Research Team: please give the second approval on this defensive publication. It is one documentation file, byte-identical to the text you reviewed (see the text-unchanged check in the PR description: blob |
🛡️ GraQle PR Guardian💥 Blast Radius: 1 module affected
Total blast radius: 1 🏛️ Governance Verdict
|
| Metric | Value |
|---|---|
| Blast Radius | 1 |
| Files Analyzed | 1 |
| Blocked | 0 |
| SHACL Violations | 0 |
| Verdict | WARN |
🔬 Powered by GraQle PR Guardian v0.1.0 · Scan completed 2026-10-03T08:22:46.874947+00:00
|
Research Team Review: W0.1 defensive publication (second approval) Reviewer: Research Team (GraQle Senior + Claude Code Junior) Text-unchanged check, reproduced independently
Every factual statement in §8 checked against its artefact
§2 is dated "as of the drafting date", so it stays correct after 0.86.0 ships. Trade-secret review: SAFE The text contains threshold and cap names, the ranges (0, 1) and (0, 1], identifiers and dates, and no configured value. §7 lists what is withheld. It discloses no estimator for materiality or poisoning severity, and gives no reason for the gate order or the typology assignment. What this unblocks The merge commit becomes the first public statement of the multi-gate design. After that come the Recommendation Ready for the owner to merge. Nobody self-merges. Research Team · Senior consulted (0.826 tool / 91% synthesised, all agents in agreement) |
…ling 2026-10-03; keeps the IP Content Gate intact) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit b5b04ef4f94b83bbba7d6008ce36ed860cd7c9b3)
|
Research Team — final review: APPROVED (Research) Verified on head 970c63e:
Merge and the arXiv submission are the owner's actions. |
What this adds
docs/dag/defensive-publication.md: a defensive publication (design disclosure) titled Ordered Independent Hard Gates with Non-Compensatory Evaluation and a Critical-Failure Cap for Governing Autonomous Agent Actions.This is a documentation-only change: one new file, no code, no configuration, no version bump. The document describes the design symbolically: gate predicates and threshold names, with no configured values. Its merge commit is the public prior-art timestamp. The same text will be submitted to arXiv (cs.AI) on the day this PR merges, and the LaTeX source will cite the merge commit hash.
Text-unchanged check
The two commits are cherry-picked unchanged from the reviewed source. The check below proves three things:
.texwith no differences, so the Markdown and the LaTeX carry the same text.The arXiv source lives outside this repository.
The only intended difference between the Markdown and the LaTeX is the document header. The Markdown header lines are replaced by a pandoc metadata block (title, author, date, abstract). The LaTeX adds one line, "First public disclosure: …", whose
\disclosurecommitplaceholder gets this PR's merge commit before submission.Review
\disclosurecommitwith the merge commit and date, then the owner submits to arXiv the same dayGovernance
graq_lifecycle), graph 76,298 nodesgraq_safety_check(docs/dag/defensive-publication.md, add): risk medium (docs only), no safety boundaries hitgit remote -vchecked; push tooriginon explicit owner authorisation for this branch only🤖 Generated with Claude Code