fix: point to the Seshat cluster, add ground-system correction block#59
Merged
Conversation
Phase H/I of the Phase 1 UX coherence fix pass. README.md: vocabulary 62 -> 61 in the ecosystem table. The five-repo "Built by Liminate" table was internally accurate but offered zero path to the separate Seshat product cluster (seshat-app, liminate-mcp, liminate-invariant) despite it existing — added one bridging sentence pointing to the seshat-app repo and liminate.dev/seshat, without surfacing the private liminate-dev repo. audit/03_ground_system_correction.md (new): the durable ground-system correction per decision #4 and finding F1-10. F1-10 cites a locked source ("section 4.1 — Ink, #0B1C38, Agreements") that this session could not locate despite five vault searches — the closest candidate document has a different section 4 entirely and predates Seshat/ Translate/Sentinels. Recorded here as the durable artifact instead of guessing at a location, same role 02_remediation_tracker.md plays for Phase 0, with the search disclosed and an open question left for Rob to point to the real document if one exists. The correction itself (Night/Paper/Ink/Seshat-amber, Ink now covering four platform apps) was built from this session's own live verification, not invented. Documentation only — no surface was repainted to produce it.
rmichaelthomas
added a commit
that referenced
this pull request
Jul 15, 2026
fix: point to the Seshat cluster, add ground-system correction block
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
Phase H/I of the Phase 1 UX Coherence fix pass (build prompt executed against
phase1_ux_coherence_findings.md/phase1_remediation_tracker.md).seshat-apprepo andliminate.dev/seshat, without surfacing the privateliminate-devrepo.includesconnective andremoveverb #4 and finding F1-10. F1-10 cites a locked source ("§4.1 — Ink,#0B1C38, Agreements") that this session could not locate despite five vault searches — the closest candidate document has a different §4 entirely and predates Seshat/Translate/Sentinels. Recorded here as the durable artifact instead, same role02_remediation_tracker.mdplays for Phase 0, with the search disclosed and an open question left for Rob to point to the real document if one exists. The correction itself (Night/Paper/Ink/Seshat-amber, Ink now covering four platform apps) was built from live verification this session, not invented. Documentation only — no surface was repainted.Test plan
🤖 Generated with Claude Code