docs: canonize All Gods Must Die doctrine and exact-object completion amendment - #80551
docs: canonize All Gods Must Die doctrine and exact-object completion amendment#80551andrexibiza wants to merge 5 commits into
Conversation
Signed-off-by: andrexibiza <84248988+andrexibiza@users.noreply.github.com>
Signed-off-by: andrexibiza <84248988+andrexibiza@users.noreply.github.com>
Signed-off-by: andrexibiza <84248988+andrexibiza@users.noreply.github.com>
alt-glitch
added
type/docs
Adds Amendment I, the sixth law, completion-record schema, webhook state ledger, guide, successor composition source, release manifest, and interlock refinement. Signed-off-by: Andrex Ibiza, MBA <84248988+andrexibiza@users.noreply.github.com>
Remove implied binary repository publication from the guide and update the release-manifest digest to the exact guide bytes. Signed-off-by: Andrex Ibiza, MBA <84248988+andrexibiza@users.noreply.github.com>
andrexibiza
changed the title
Task Completion Verification — exact-object publication receiptThe architecture amendment is now source-controlled on this PR at exact head The doctrine now carries the sixth law:
Exact-head read-back receipts:
Exact-head workflow state at read-back:
No green state is inherited from the prior head. The PR is open, non-draft, mergeable, and unmerged. The 14-page amendment PDF and 83-page composed v1.1 PDF are locally preflighted/rendered outputs whose digests are recorded in the release manifest; this comment does not claim those binaries are present in the GitHub tree. |
Exact-head workflow updateCurrent state for exact source head
The CI job page available through the connector shows every exposed job as success/skipped, including the Docusaurus build, attribution, supply-chain checks, e2e, macOS/Windows tests, ruff, and the exposed Python slices. The run-level conclusion is nevertheless red, so a later-page/aggregate job remains failing and is not exposed by the connector's first-page job response. Accordingly: the amendment sources are submitted and exact-object read back at this SHA; Docker and Nix are exact-head green; the PR remains open, non-draft, mergeable, unmerged, and CI-red. No all-green or merge-complete claim is made. |
Canonical architecture issueThe complete doctrine, state model, evidence contract, webhook case study, source ledger, release semantics, acceptance matrix, and interlock topology are now presented in #91230. This PR remains the exact implementation/publication object. #91230 is the architecture and lifecycle-contract node; it does not inherit acceptance, merge, release, or CI state from this PR. Related #91230 |
2 participants
What this contribution is
This PR canonizes All Gods Must Die: Adversarially Verified Transformation as a first-class Hermes publication, guide, reusable production skill, and versioned architecture doctrine.
The original paper unifies god-file decomposition and multilingual documentation parity under one rule:
Hermes is the system under study: a stateful, self-regulating cybernetic agent whose LLM layer supplies neural plasticity and whose deterministic skeleton — CI gates, cryptographic hashes, graph checks, seam identity, manifests, approval boundaries, memory/profile isolation, and adversarial witnesses — makes that plasticity answerable to structure.
Hermes is explicitly framed as a weapon for sovereignty, not war: an instrument for preserving user agency over model choice, context, memory, tools, execution, provider routing, and technical records. Cyber defense is an internal function because Hermes lives inside the CLI, gateway, tool, memory, provider-egress, desktop-auth, documentation, and CI surfaces she defends.
Amendment I — Task Completion Verification
This PR now embeds a successor architecture refinement derived from the concrete
Task Completion Verificationexecution record.The original five laws gain a sixth:
Derivative rule:
This closes the activity-completion collapse failure class: a prepared patch is not a changed branch; a changed branch is not a pull request; a pull request is not approval; approval is not merge; merge is not release; release is not operational proof.
Completion is represented as a typed state vector across:
The amendment preserves the original god-file campaign's
SHIPPEDdefinition as the namespaced predicateKAG_SHIPPED. It does not implyMERGED,PUBLISHED,RELEASED, orOPERATIONALLY_VERIFIED.The webhook case study preserves both time-bounded truths:
403 Resource not accessible by integration; no public state changed in that execution;The later target objects do not retroactively turn the earlier 403 into a successful write. The earlier blocker does not deny the later target state. Both events remain in the mutation journal.
Publication surfaces
Original v1.0 contribution
website/docs/guides/all-gods-must-die.md— long LLM-readable guide, registered in the Guides & Tutorials sidebar.docs/research/all-gods-must-die-adversarially-verified-transformation.pdf— immutable 68-page compiled publication.docs/research/all-gods-must-die-adversarially-verified-transformation.tex— reproducible LaTeX source.docs/research/all-gods-must-die-adversarially-verified-transformation.bib— merged bibliography.skills/research/long-document-production/SKILL.md— reusable long-document production skill.website/scripts/generate-llms-txt.py— curatedllms.txtinclusion.Task Completion Verification source-controlled surfaces
website/docs/guides/task-completion-verification.md— exact-object completion architecture guide.docs/research/task-completion-verification-amendment.md— canonical source-readable Amendment I.docs/research/all-gods-must-die-adversarially-verified-transformation-v1.1.tex— successor composition source preserving immutable v1.0 and appending Amendment I.docs/research/task-completion-record.schema.json— machine-auditable completion-record contract.docs/research/task-completion-verification-ledger.json— dated local-blocker and current GitHub reconciliation records.docs/research/all-gods-must-die-v1.1-release-manifest.json— source digests, generated-output digests, typed lineage, and packaging-time truth.docs/research/all-gods-must-die-interlock.md— contribution graph and lifecycle boundary.Generated release outputs
The amendment PDF and composed v1.1 PDF were built, preflighted, rendered, and visually inspected locally. Their digests are recorded in the release manifest. Their GitHub binary publication is not asserted by this PR source update.
1a8f46528faf10339e7d0cdeb3cf0b8035b341a23ffbde2b0b7aa19e361505f5.be5f9c912025eb2fbbcbcef2a497eb76f041db7ecfa6637550fe7bbae1fb805b.Hermes-agent security hardening evidence
The paper documents the actual Hermes-agent security series:
#77008— Bitwarden encrypted-only disk cache and legacy plaintext migration/removal.#77012,#77020— exact-value protection in status lines and logs.#77179,#77185,#77198— applied-secret provenance and exact-value provider-egress masking.#77027,#77181,#77193— child-process environment scrubbing, including renamed and arbitrary external secrets.#77528,#78033,#78036— TUI compute host, LSP, plugin sidecar, andshell.execscrub-bypass closure.#77527— real Windows ACL protection throughicacls, including the existing-file mode-preservation branch.#77039— hermetic end-to-end no-exfiltration acceptance gate through the real secret-loading entrypoint.#77031— credential-read scope audit whose correct result was no fabricated code change.#76958,#78901–#78904— stale desktop session-token clobbering, provenance diagnostics, bounded retry, and real subprocess regression harness.#78806— refusal to mutate git-managed state inside a real.gitdirectory.Interlock and contribution graph
Current contribution:
#80551.Part of #78647 — graph-gated engineering / large-file decomposition tracker.
Related sibling contributions:
#79609—godfile-kill-campaigns, the 5×2×3 blind-witness decomposition skill.#79779—campaign-operations-kill-locks, the bidirectional audit and KILL LOCK skill.#79898—feature-parity-alignment-campaigns.#80391— cross-language docs germination pipeline.#80392— cross-language docs germination EPIC.#60535/#63660— French documentation issue and seed provenance.#85002— Task 7 case-study object.#85523→#90236— Task 10 historical provenance and canonical successor.The interlock manifest defines the required edges:
Part of #78647binding.Related #Nlines.related_skillsand the in-repo skill path.derives_from/refineslineage.Interlock is bidirectional or incomplete. Completion is exact-object bound or unproven.
Attribution
Axl Ibiza, MBA authored the doctrine, architecture, campaign design, source selection, editorial direction, and acceptance standard. The artifact preserves contributor, reviewer, agent, and source-project attribution rather than collapsing every action into one false authorship claim.
All contributions matter: feature code, security hardening, tests, audits, documentation, translations, skills, reviews, ledger repairs, interlock corrections, provenance work, negative receipts, and truthful blocker reports. Attribution is a core value and a correctness edge.
Verification
Original publication
skills/research/long-document-production/SKILL.md.Axl Ibiza, MBA.website/sidebars.tsand the curatedllms.txtgenerator.Amendment and exact-object source submission
048606e79810a42fcc243e2ae30373c91eacf574.Acceptance
The paper, guide, source, bibliography, interlock manifest, long-document skill, Amendment I, completion schema, ledger, successor composition source, and release manifest are one contribution graph. Do not merge them as isolated files.
Part of #78647
Related #79609
Related #79779
Related #79898
Related #80391
Related #80392
Related #60535
Related #63660
Related #85002
Related #85523
Related #90236
Signed-off-by: Andrex Ibiza, MBA 84248988+andrexibiza@users.noreply.github.com
Part of #60535
Part of #80392