Guillaume Descoteaux-Isabelle

Query builder for relational webs with Indigenous protocol awareness — traversal, accountability, OCAP® compliance

Abstract storage layer for Medicine Wheel data with JSONL and Neon backends, plus a future Redis path.

Shared Redis data-access layer for the Medicine Wheel Developer Suite — connection management, Node/Edge/Ceremony CRUD, session-ceremony linking, and discovery helpers

Eyes & ears of agent-supported film production — witness a belt-device recording as typed perceptual events and seed a production knowledge graph

Typed HTTP client for a Medicine Wheel — nodes, edges, ceremonies, beats and the ceremonial diary — with the wheel's paging honesty carried through (count, total, truncated) and fail-fast errors that name the status.

Temporary package placeholder for staged publishing

HTTP access to the Miadi voice layer — the /api/voice envelope, the two-name token tier, and a dependency-free fetch client. Publishes voice from any process that is not the server.

Miadi voice layer — Edge-TTS producer, persona/voice map, KV-backed ledger, and the #457 channel adapter (Assembly-Voice absorption).

Read a capture's transcriptions by form and intent: label-grammar parsing, prose segmentation, and the semantic-correction advisory that warns and never rewrites. Reads both shapes — the episode-capture folder the recorder writes today and the legacy gmte

Chronicle ATTENTION without a framework: the item vocabulary, the panel's behaviour as plain functions, its visual specification, an HTML-string renderer for servers, and a vanilla DOM mount. @miadi/attention-ui is the React host over the same core. Nothi

The React host of @miadi/attention-core for reviewing and answering Chronicle ATTENTION items. Core owns the vocabulary, behaviour and visual specification; this package owns React state and events. No component owns a URL, token, filesystem root, or medi

Relate and sync IAIP inquiry artefacts, their GitHub issues, and miadi-chronicle episodes. Creates vessels and relations only — never inquiry content.

Browse the Miadi Chronicle from a terminal and take part in its talking circles: list and filter every episode, search their text, read a vessel's files with their references as chips, open the room, the wheel or the vessel as clickable links or a QR code

The tracing service layer of the Miadi Factory: three domains (ceremony, story, eng), five resources (trace, prompt, session, dataset, score-config), the miadi-tracing:<domain>/<resource>/<id> reference, and the provider contract an app consumes without k

Langfuse as a Miadi tracing provider: one Langfuse project per domain (ceremony, story, eng) read through <DOMAIN>_LANGFUSE_PUBLIC_KEY, _SECRET_KEY and _BASE_URL, answering the @miadi/tracing provider contract with metadata only. The app consumes @miadi/t