Miadi-18

Miadi

Miadi is a relational software-factory monorepo: a place where agents, packages, chronicles, hooks, voice, music, capture, inquiry, memory, and foundations are organized so they can be reused without losing their context.

The old landing text treated this repository as a sunset/donor archive. That was useful at the time, but this repository has since become active again as a package lattice and documentation surface.

Start here

• Human landing page: this README.
• LLM compact map: llms.txt.
• LLM full operating map: llms-full.txt.
• Package index: packages/llms.txt.
• Package work area: packages/.
• RISE/RISPEC notes: package-local rispecs/ folders.
• Security reporting: SECURITY.md.
• Deployment and access changes: docs/security-deployment.md.

Active platform and current work

app/ contains the web platform and APIs, including community identity, ceremonies, Chronicle views, and agent/session interfaces. packages/ contains reusable workspace components; runtime/ contains runtime integrations; mcp_server/ provides local and HTTP tool transports. Their manifests, source, tests, and launch contracts establish current behavior.

The September 2026 security audit tracks public-repository exposure, application permissions, VPN/public ingress, and installation hardening. Source fixes still require deployment verification. Documentation refresh #667 tracks reconciliation of older guides and package indexes. The older sections of ROADMAP.md are historical planning, not a verified description of the current platform.

When published through the docs site, the same shape should resolve as:

• https://docs.miadi.jgwill.com/
• https://docs.miadi.jgwill.com/llms.txt
• https://docs.miadi.jgwill.com/llms-full.txt
• https://docs.miadi.jgwill.com/packages/llms.txt
• https://docs.miadi.jgwill.com/packages/<name>/README.md
• https://docs.miadi.jgwill.com/packages/<name>/rispecs/RISPEC.md

What Miadi contains

• Hooks — event envelopes, sessiondata interpretation, gateway boundaries, and artifact composition seams.
• Capture — durable recording/take lifecycle, capture clients, capture service, and React capture UI.
• Voice — persona-aware voice production, HTTP clients, and MCP voice access.
• Ava8 / music — ABC notation, rendering, playback, MIDI, React score components, and composition bridges.
• Memory / inquiry / chronicle — episodic-memory schemas and relations between inquiries, GitHub issues, compositions, and chronicle episodes.
• Foundations — public research/foundation packets, including the Wampum Narrative Engine foundation beacon.
• Utilities — Node service helpers, orchestration helpers, STC automation, and workbench areas.

Working with packages

Use the package index before choosing an install target:

pnpm add @miadi/<package>
npm install @miadi/<package>

Inside the monorepo:

pnpm install
pnpm --filter @miadi/<package> build
pnpm --filter @miadi/<package> test

Do not assume every packages/* directory is installable. Some directories are workspace/spec areas, some packages are private, and some are stubs or release-unclear. packages/llms.txt is the authority map for that distinction.

RISE / RISPEC

RISE means Reverse-engineer, Intent-extract, Specify, Export.

Package-local specs live at:

packages/<name>/rispecs/RISPEC.md
packages/<name>/rispecs/README.rise.md

These specs are behavior maps for humans and agents. Package metadata, README examples, type declarations, tests, and source remain the higher authority for exact runtime details.

Principle

Miadi should make technical work reusable without pretending that code is context-free. The goal is practical package clarity with enough relational memory to explain why each package exists, how it connects, and what must not be guessed.