ring-105: ecosystem .tri rewrite (7 repos -> t27 SSOT)#1454
Draft
gHashTag wants to merge 7 commits into
Draft
Conversation
…epic + final report 11 weaknesses W-A..W-K across 7-repo ecosystem (t27/trinity/trios/trios-mcp/ 999-multibots-tma/999-multibots-telegraf/IGLA). 5 HIGH, 3 partial mitigation. Negative-first literature review with 68 citations. Epic decomposed into 8 ring-105-XXX branches. Toxic verdict + 3 forward roads + 3 collaboration variants. ASCII, banned-hype clean. Closes #1452 Refs #1453
…) .tri mozg.tri: cognitive state FSM (short_term + long_term slots, tick(stimulus)). dna.tri: persistence + provenance (spec_hash, gen_hash, ancestor chain). Schema-first upstream SSOT for the Trinity organism model. Refs gHashTag/trinity#604 Refs #1453
Small SSOT for Tool { name, version, args_schema, returns_schema,
side_effect_class }. Any MCP server can consume, including trios-mcp.
Schema-first, three invariants, eight tests.
Refs gHashTag/trios-mcp#7
Refs #1453
scene_schema.tri: generic scene FSM (message envelope + state transitions). ring_runtime.tri: generic ring-worker (backoff policy + lease + heartbeat). Both anonymised: no PII, no wallets, no bot tokens, no user IDs, no tariffs. Schema-first upstream SSOT for downstream multibot / worker systems. Refs gHashTag/trios#1083 Refs #1453
…seed pairs
Manifest schema: Pair { id, spec_path, metadata_path, spec_hash, meta_hash,
gen_target, license }, three invariants, eight tests.
v0.1 seed: 8 pairs derived from ring-105-001..007 pilots, per-pair SHA-256
in MANIFEST.json, DECONTAM.md log, README.md. Total ~7-10K tokens, ~31 KB.
Honest capacity note: ~3 orders of magnitude below phi-1-small ~350M-param
compilable-code floor. W-18 (data-starvation) stays HIGH. Not training-ready;
schema-first seed only.
Closes #1451
Refs #1453
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This was referenced Jul 10, 2026
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.
ring-105: ecosystem .tri rewrite (7 repos -> t27 SSOT)
Draft PR. Info-drop, no merge urgency. Async-only.
Summary
Landing schema-first .tri specifications derived from a 7-repo ecosystem
(t27, trinity, trios, trios-mcp, 999-multibots-tma, 999-multibots-telegraf,
IGLA) as upstream SSOT under
specs/**in gHashTag/t27.Hard rule enforced: no hand-written .zig/.rs anywhere in this PR. All
targets are auto-generated from .tri or marked STUB. Every commit carries
a spec_hash-friendly path; no logic duplication between spec and code.
Commits (7 atomic, one per ring)
docs/wave_ecosystem_2026-07-08/*(5 files)specs/experience/experience.trispecs/organism/{mozg,dna}.trispecs/git/orchestrator.tri(zig target)specs/mcp/tool_registry.tri(rust STUB)specs/scenes/scene_schema.tri+specs/runtime/ring_runtime.trispecs/dataset/igla_coder_manifest.tri+dataset/igla-coder/v0.1/**Layout discussion (no code): Refs #1453.
Honest limits (do not spin)
sandbox; t27c parse of the 8 new .tri files is not yet verified locally.
tokens is ~3 orders of magnitude below the phi-1-small ~350M-param
compilable-code floor (Chinchilla-optimal for even a 500K-param model
would be ~10M tokens). Not training-ready; schema-first seed only.
surface is labelled partial in STATUS.md.
wallets, no bot tokens, no user IDs, no tariff codes.
Weaknesses openly recorded
docs/wave_ecosystem_2026-07-08/WEAKNESS_AUDIT.mddocuments 11 weaknessesW-A..W-K across the 7-repo ecosystem, of which 5 are HIGH severity and
3 carry partial mitigation. This PR does not close any of them.
References
t27/CLAUDE.md(PHI LOOP)t27/CANON.mdNot asking
No merge urgency, no review deadline, no reply obligation. Marking Draft
so the PR is visible and citeable without gating the master branch.