docs: correct false lithoglyph tombstone (no lith monorepo) - #44
Merged
Merged
Conversation
…n to lithoglyphdb/gnpl/glyphbase pending)
🔍 Hypatia Security ScanFindings: 251 issues detected
View findings[
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in instant-sync.yml",
"type": "missing_timeout_minutes",
"file": "instant-sync.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
5 tasks
hyperpolymath
added a commit
that referenced
this pull request
Sep 25, 2026
…sim-core AFFIRMATION, lithoglyph/gnpl disentanglement, K9 pedigree + trusted-base (#105) Closes #42, closes #45, closes #53 ## Foundational, at source, upstream/downstream, enduring This PR addresses all three open issues foundationally, not symptomatically. ### #42 — Template debt + ReScript/TS→AffineScript + verisim-core AFFIRMATION **Template debt root cause:** had placeholder — template default not customised. **Fix at source:** - fixed: real unique-strength description (coordination of four families with honest boundaries), 7 divergent-invariants, 6 known-constraints, v1.1.0 2026-09-25 - SPDX warnings fixed: + now have SPDX headers — A2ML validation 36 files 0 errors 0 warnings (was 2 warnings) - v0.2.0 with enduring guards **Downstream:** - 2026-09-25 supersedes 2026-06-19: 0 placeholder files, 0 .res/.ts, K9 passes, proof-debt documented, verisim-core AFFIRMATION exists - 2026-09-25: MUST includes coordination-only + placement guard + K9 + trusted-base; INTEND marks DONE - rewritten to coordination focus - v0.2.0 with foundational-fixes section **ReScript/TS migration:** - 0 → 0 in coordination paths (was 143 + 4 package.json) - DONE via extraction: lithoglyph 819 files → hyperpolymath/lithoglyph, glyphbase → glyphbase, gql-dt → gnpl, verisimdb → verisimdb - updated to DONE with completion summary - Mustfile: no-typescript critical, no-rescript critical (new), no-npm-package-json warning (new) **verisim-core AFFIRMATION:** - Created with verifiable anchor, what is solid (structure, SPDX, no banned patterns, Ed25519 real, federation enforcement, 55 assertions), known-incomplete, reproduce, one-line, cross-repo wiring, joint attestation - Satisfies Issue #42 requirement: shippable layer needs own AFFIRMATION with scoped table ### #45 — Lithoglyph / GNPL / Glyphbase extraction **Root cause:** reservation repos exist but content still in lithoglyph/, prior lith monorepo was unauthorised fabrication (#44), GNPL and LithoglyphDB entangled — design decision needed. **Fix at source — design decision (not mechanical):** - Created : - Table: LithoglyphDB = journal/storage/reversibility/proof registry vs GNPL = narration/projection (accounts, stances, warrants, rival) - Why separate, what superseded (core-factor/gql/ is superseded, not migrated) - Extraction table: was → now, files, status - History preservation: split-history/lithoglyph 819 files 68 commits, split-history/verisimdb 713 files 124 commits, _split_gnpl branch, never prune - Glyphbase own repo rationale - Enduring guards upstream/downstream/cross-repo - Acceptance criteria all DONE, naming note (issue says lithoglyphdb but canonical is lithoglyph) **Downstream — extraction DONE:** - lithoglyph 819 files 2026-07-27, verisimdb 713 files 2026-08-03, gnpl 125 files PR #4 102c79e, glyphbase 130 files — pointer READMEs left - + document split-history tags **Enduring:** - placement-guard.yml: lithoglyph/verisimdb now FAIL (not warn) on new files; grandfathered quandledb/nqc/typeql-experimental/verisim-core/verisim-modular-experiment warn - block-db-writes.sh blocks NEW files in legacy DB dirs - 0-AI-MANIFEST.a2ml coordination-only invariant, CLAUDE.md NEVER/ALWAYS, Trustfile extraction section - REGISTRY.adoc clarified lithoglyph vs lithoglyphdb naming - RESITE status PARTIAL DONE ### #53 — K9 pedigree + trusted-base **K9 root cause:** verisimdb/connectors/test-infra/deploy.k9.ncl used let indirection valid Nickel but early validator couldn't follow; validator fixed to resolve one-hop let; file removed 2026-08-03 after verisimdb extraction. **Fix upstream:** validate-k9.sh now handles let alias (pedigree_alias sed + let block opener), comment explains. **Downstream:** remaining 7 K9 files under .machine_readable/svc/k9/ all have metadata.name, validation passes 7 files 0 errors. **Enduring:** Mustfile k9-pedigree-valid critical, placement guard, governance.yml reusable workflow, Trustfile k9-pedigree integrity. **Trusted-base root cause:** proof-bearing files in monorepo era, no docs/proof-debt.md. **Fix:** Created docs/proof-debt.adoc with current status (coordination repo has no proof-bearing impl after extraction), historical #53 resolution, escape hatch inventory (0 in coordination paths), policy for new debt (// TRUSTED: reason review date issue), verification commands, refs hypatia#464. **Enduring:** Mustfile proof-debt-documented critical + no-believe-me + no-unsafe-coerce critical, Trustfile trusted-base + proof-debt-gate, AGENTIC.a2ml constraints, docs/governance/K9-PEDIGREE-TRUSTED-BASE-FIX.adoc. ### Verification 2026-09-25 - K9: 7 files 0 errors 0 warnings - A2ML: 36 files 0 errors 0 warnings - Template: 0 placeholder files (excluding intentional guard lists) - ReScript/TS: 0 files - Banned patterns: 0 in coordination paths - proof-debt.adoc exists, verisim-core/AFFIRMATION.adoc exists, disentanglement exists, K9 fix exists, AFFIRMATION updated ### Files changed 20 files, 1193 insertions: methodology.a2ml, ANCHOR.a2ml, Mustfile.a2ml, Trustfile.a2ml, AGENTIC.a2ml, STATE.a2ml, 0-AI-MANIFEST.a2ml, Justfile, REGISTRY.adoc, TEST-NEEDS.adoc, AFFIRMATION.adoc, FOUNDATIONAL-FIXES-2026-09-25.adoc (NEW), K9-PEDIGREE-TRUSTED-BASE-FIX.adoc (NEW), musts-intends-wishes.adoc, LITHOGLYPH-GNPL-DISENTANGLEMENT.adoc (NEW), RESCRIPT-TS-AFFINESCRIPT-MIGRATION.adoc, RESITE-DATABASES-TO-OWN-REPOS.adoc, proof-debt.adoc (NEW), verisim-core/0-AI-MANIFEST.a2ml, verisim-core/AFFIRMATION.adoc (NEW) --------- Co-authored-by: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
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
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.
The
lithoglyph/MOVED.mdfalsely announced a move to alithmonorepo. Owner-disavowed — that consolidation was never authorised andhyperpolymath/lithdoes not exist; the content (73 entries) still lives innextgen-databases/lithoglyph/.This corrects the tombstone to the truth: extraction is planned, not done, into the now-reserved repos
lithoglyphdb/gnpl/glyphbase. Stops the file misleading future readers/agents.🤖 Generated with Claude Code