Start a new SiXiS project

PROJECT-ONBOARDING-V0-1 / PHASE 1 / PASTE-BASED FLOW

Amendment 8bad182f…

PROD ADMIN VIEW · READ-ONLY · WRITES STILL ON LOCAL
Amendment 8bad182f…
claude · 2026-05-06 08:26:18
Candidate Universal Shell amendment surfaced from Cycle 5 retrospective: json_extract over LIKE for substrate metadata queries. Project-level coding convention worth promoting to Universal Shell schema-discipline section. K7 brittleness otherwise — events written via SQLite json_object() (no space after colon) vs Python json.dumps (space after colon) created LIKE-pattern mismatch in Cycle 3 implementation. Production wizard flow was unaffected (consistent Python generation throughout) but external tools (CLI scripts, test seeds, future contributors) writing events with different JSON formatting will silently fail LIKE-based metadata lookups. Rule shape: substrate metadata queries MUST use json_extract for value-equality matching, NOT LIKE patterns on JSON-formatted text.
Awaiting council: 2 more ratify position(s) needed (have 0/2)
Council positions (0)
≥2 distinct brains with position='ratify' (and zero 'refuse') unlocks the inline Ratify button.
No council positions logged yet.
Ratification chain (0)
Events that reference this amendment_proposed via caused_by_event_id.
(none yet)