Compositions
A publication needs sources, editorial judgment, and a release decision. A musical work needs its own acceptance, credits, and production records. Combining them should preserve what each contribution means and who answers for it.
A Composition gives that work a durable home. It keeps the application's records, judges its results, and governs the effects it may request. Its policies, projections, and catalogue of Patterns belong to the same reusable application across customers, Products, and deployments. Browse by the outcome you want to leave behind.
For a software question, Creation investigation retains the source, candidate and separate verdict under one bounded application contract.
The Portfolio
These Native Reference Compositions are accepted first-party application contracts and worked examples. State of Work collects their implementation evidence.
Areas
An Area groups Compositions by the kind of work you want to find. Each Area has an index leading to its applications and their outcomes.
| Area | Enter through |
|---|---|
| Creative Works | visual work, music, language editions, playable builds, and publication |
| Stewardship & Acquisition | personal health and wellbeing, places, animal care, cultivation, and acquisition |
| Presence & Embodiment | social presence, presentation, virtual worlds, physical bodies, and mobile sessions |
| Professional Operations | attributable client casework and professional handoffs |
Areas can overlap. Each Composition keeps one canonical route and owns its records and judgment; the Area supplies orientation. A Suite coordinates live work within one Area or across several. The Area contract keeps navigation separate from application ownership. Guides and Candidate studies remain separate views of explanations and proposals.
Follow a shared work
Atelier produces accepted visuals, Riffmaw music, and Language Edition aligned dialogue and captions. Broadcast admits their exact settled bundles into its timeline and judges the resulting editorial work. Its release is a separate external act.
The direction can change without erasing earlier work. A locked Broadcast master and script can enter Language Edition; the returned language bundle enters a new Broadcast Invocation for a new edition. Each owner preserves its records, acceptance, and recovery.
Settled artifacts connect these applications directly. A result that must coordinate several owners' live Invocations—commissioning work, awaiting revisions, or recovering their execution— needs a Suite. The worked handoffs extend this relationship to household care, embodied presence, and professional casework. A Product gives the resulting application or Suite a named operator promise.
Candidate studies
These studies develop application boundaries beyond the accepted Portfolio.
Thorn studies whitehat security casework: authorized assessment, bounded response during an attack, cooperative investigation, and supported reports and corrections. Monitoring supplies evidence; general system maintenance keeps its own owners.
Accounting Office studies business documents, bank reconciliation, entity-owned books, asset and subscription obligations, and period close. Provider adapters and jurisdiction profiles vary under one proposed accounting lifecycle.
Workshop tests technical-service casework. Mechanic is its proposed first Product under the passenger-vehicle service profile.
Transmuter studies the passage from imported digital material to attributed knowledge and proposals for memory and identity. Extractor and Synthesizer are its internal stages; naming, labeling, and classification belong to Extractor.
The Composition test
For a new idea, ask what should remain when the conversation ends and who can judge it finished. Then try the difficult endings: work refused, partly completed, stopped, or interrupted with an effect still unknown. Who keeps that account and decides how to recover? Choosing a Home tests whether those responsibilities need a Composition or already belong to a Product, profile, Pattern, projection, mechanism, reference, or Suite.
The companion guides follow the choices involved in shaping and combining applications:
| Question | Continue with |
|---|---|
| What operator promise does a Product offer? | Products and Suites follows a named operator promise into one configured Deployment. |
| Does this result need coordination between live Invocations? | The worked handoffs distinguish a settled foreign result from separate owners' live work coordinated by a Suite. |
| Which machinery can applications share? | Shared machinery, separate judgments keeps shared engines distinct from application records and authority. |
| Who accepts each part of a compound result? | The media comparison locates visual work, music, language editions, picture sound, and interactive world sound by acceptance rather than codec. |
How a leaf should read: authoring criteria keep each application rooted in a representative journey and falsifiable result. Lexicon owns terms; Workflow owns their architectural law.
Follow the Map to carry an application's work through the body, and Transmutation to follow creation through trial, judgment, and return.