42.19K
total weekly downloads
140 packages
@medicine-wheel/app
Medicine Wheel — Interactive visual layer for Indigenous relational research with Four Directions, ceremonies, and narrative arcs
@medicine-wheel/brainstorming
Idea into committed design through approval gates a human holds. Every outcome it emits — including its own multiple-choice questions — passes the orientation question before it is spoken. Brainstorming, ideation, requirements gathering, design review.
@medicine-wheel/capabilities
The platform-features and capabilities layer of the Medicine Wheel Developer Suite — what the platform can do, which repositories and services provide it, who said so and from what, with the 55-word statement limit and shared-capability detection
@medicine-wheel/ceremonial-diary
Ceremonial Diary — a participant's voice across the Five-Phase ceremonial methodology. Intention, observation, and reflection entries with pattern detection, statistics, markdown export, and optional projection into the chronicle wheel. Persists through @
@medicine-wheel/ceremony-protocol
Ceremony lifecycle protocol for Medicine Wheel — manages ceremony state, phase transitions, governance enforcement, and ceremonial review workflows
@medicine-wheel/client
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.
@medicine-wheel/community-identity
Who is in the circle: people as wheel nodes, roles with a permission map, circles and memberships as relations, invitations and self-issued credentials kept by the consumer — so a Medicine Wheel can tell two people apart.
@medicine-wheel/community-review
Community-based ceremonial review protocol for Medicine Wheel — review circles, consensus and relational accountability, after the community-grounded credibility Wilson describes; the Elder step is the package's own design
@medicine-wheel/consent-lifecycle
Ongoing relational consent lifecycle for the Medicine Wheel Developer Suite — consent as a living relational obligation, not a boolean checkbox
@medicine-wheel/creative-orientation
The orientation question, asked before the work: is there a prior state you are restoring? Yes: a gap analysis, which looks for what is missing, can be useful; it is not part of the creative orientation, and the turn after it leads to a structural tension
@medicine-wheel/creative-problem-solving
Creative problem solving, routed at the door: name the prior state you are restoring. Named one: a gap analysis looks for what is missing against it, and the turn to the creative orientation follows. Named none: you are creating, and structural tension is
@medicine-wheel/data-store
Shared Redis data-access layer for the Medicine Wheel Developer Suite — connection management, Node/Edge/Ceremony CRUD, session-ceremony linking, and discovery helpers
@medicine-wheel/data-store-postgres
PostgreSQL/Neon provider scaffold for the Medicine Wheel Developer Suite — shared pool management and provider-ready storage entrypoints
@medicine-wheel/developer-repository-mapping
Repository mapping for the Medicine Wheel Developer Suite — owner hubs of JSONL rows in <owner>/<owner>/.miadi/repository-mapping/, a lifecycle state machine checked against git, a meta mapping that reads other hubs without copying them, the projection in
@medicine-wheel/dummy
@medicine-wheel/episode-ui
The episode-vessel files workspace — browse, read, preview markdown, edit in CodeMirror with a full-screen mode and a conflict that never loses the draft — framework-free so a plain page and a React app mount the same one. Plus React components for a cere
@medicine-wheel/episode-vessel
The file law of a chronicle episode folder, written once: bounded contained listing, text read and revision-guarded atomic write, ceremony notes and ceremony file attachments. No HTTP, no React, no service URL — a phone, a Next.js route and a test open th
@medicine-wheel/events
The events a Medicine Wheel writes — catalog, MiadiEventEnvelope, JSON Schema and AsyncAPI document, the append-only events.jsonl log, the publisher seam a broker plugs into, and git carriage with a follower (mw-events)
@medicine-wheel/fire-keeper
Fire Keeper coordination agent for Medicine Wheel — tends the ceremony fire, ensures relational integrity through gating conditions, and maintains Wilson alignment as an active agent
@medicine-wheel/gap-analysis
A gap analysis looks for what is missing: evidenced baseline, observation, difference, verifiable elimination steps. Useful when something worked and stopped (root cause, incidents, regressions, troubleshooting). It is not part of the creative orientation
@medicine-wheel/github-ceremony
GitHub-ceremony processing — witness GitHub webhook events (issues, pull requests, merges, commits) through a ceremonial lens and record them as relational ceremony beads. Pure, framework-free functions that take a parsed payload and a @medicine-wheel/sto
@medicine-wheel/graph-viz
Medicine Wheel graph visualization — circular layout with four-direction node positioning, ceremony-aware edges, and OCAP® indicators
@medicine-wheel/hello-world
A dummy public package for testing npm publish functionality.
@medicine-wheel/honcho
The wheel's projection into Honcho — beats and ceremonies become Honcho messages, a speaker's evolving representation is recalled, and a derived conclusion is written back as a knowledge node. The wheel stays canonical; Honcho holds what the history has c
@medicine-wheel/importance-unit
ImportanceUnit — the relational unit of knowledge for the Medicine Wheel Developer Suite. Carries epistemic weight, source dimensions (Land/Dream/Code/Vision), circle depth tracking, and accountability links grounded in Wilson's relational epistemology