Weksa/schemas
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Weksa c1b2778b15 Merge weksa-lowering/speaker-state into main; adapt the lowerer to admit-only LoweringInput
No textual conflict except data/interlingua/inventory.cc (binary): regenerated as
the branch's rev 1 (61 entries) plus `weksa inventory proof` (rev 2, 7 entries).
Semantic breaks fixed: proof_packet() carries an empty Stance; `weksa lower`
re-admits the stored packet (idempotent) because validate no longer returns the
view; tests/lower.rs builds views through PacketStore::admit; seed_reseeded
expects seed plus proof revision. AGENTS.md records the CARGO_HOME requirement
and the proof packet key.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 15:54:42 +00:00
..
cultnet Merge weksa-lowering/speaker-state into main; adapt the lowerer to admit-only LoweringInput 2026-11-03 15:54:42 +00:00
cultural-ontology-profile.md Define nested cultural ontology profile state 2026-06-09 16:40:31 +01:00
english-lowering-packet.md Refocus lowering on English projection 2026-05-19 16:09:35 +01:00
english-pronunciation-plan.md Define speech lowering handoff 2026-05-19 16:35:41 +01:00
interlingua-packet.md entity-store (2c): referents cite entity ids; typed entity store with bounded NFC forms per language; corpus name spans on grapheme boundaries; required CorpusItemId; packet schema v3 (squash of weksa-lowering/entity-store 29d671e..ea2c96c; Soul s1, s2) 2026-10-29 17:14:06 +01:00
language-project-state.md Scaffold persistent state spine 2026-05-16 03:43:43 +01:00
project-state.md Scaffold persistent state spine 2026-05-16 03:43:43 +01:00
README.md Define nested cultural ontology profile state 2026-06-09 16:40:31 +01:00
target-language-cultural-ontology.md Define nested cultural ontology profile state 2026-06-09 16:40:31 +01:00
utterance-embedding-handoff.md Validate tiny PanPhon handoff fixtures 2026-06-03 12:29:22 +01:00
utterance-lowering-packet.md Add MiMo speech provider target contract 2026-06-11 19:17:02 +01:00

Schemas

This folder records Weksa's persistent state contracts in human language.

The repo deliberately starts without general executable schema code. Runtime language, storage backend, and generated type targets are undecided. Until those decisions are made, this folder is the receipt surface: if a state shape matters enough to steer the machine, describe its authority here.

Narrow fixture validators may exist when an external handoff needs an executable proof. They do not become the schema authority unless the map explicitly promotes them.

Canonical Surfaces

  • project-state.md: project map, scratch, decisions, evidence, and open questions.
  • language-project-state.md: future per-language state for ontology, grammar, morphology, phonology, diachrony, and renderer configuration.
  • interlingua-packet.md: shared meaning packet contract between clients, authoring tools, and language projects.
  • utterance-lowering-packet.md: shared packet contract for lowering interlingua and projected speaker context into one or more target-language utterance realizations.
  • target-language-cultural-ontology.md: contract for the address, politeness, register, idiom, metaphor, script, and forbidden-flattening profiles consumed by target lowerers.
  • cultural-ontology-profile.md: nested CultCache profile contract for cultural ontology, including typed salience axes, linguistic affordance feature records, evidence, activation gates, and lowering traces.
  • english-lowering-packet.md: packet contract for the older English-specific realization lane.
  • english-pronunciation-plan.md: plan for stringing flavored English into IPA/phoneme sequences before downstream speech.
  • utterance-embedding-handoff.md: learned utterance embedding handoff contract for handing prosody, emphasis, and character pressure to downstream synth control.

Source Of Truth

  • state/map.yaml is the canonical live map for this workspace.
  • state/scratch.md is temporary working memory.
  • schemas/ explains the contracts.
  • Future executable schemas must be generated from or reconciled with these receipts in the same pass that introduces them.