Package anatomy

Three descriptions, three audiences

The listing is not executable. The authoring brief is not runtime authority. The package manifest is parsed into a strict versioned contract before any artifact can run.

Typical project

vertical-experience/
├── chasing-mastery.package.json
├── chasing-mastery.listing.json
├── chasing-mastery.authoring.json
├── src/
│   ├── package.ts
│   ├── engine.ts
│   ├── ui.ts
│   ├── presentation.ts
│   ├── overlay.ts
│   ├── coordination.ts
│   └── narration.ts
├── fixtures/
└── .chasing-mastery/

Contributions point to artifacts

An activity contribution identifies its configuration schema, result contract, accepted commands and observations, worker artifact, optional player artifact, progression, Story Events, and correction policy. Coordination and narration are separate contributions because they answer separate policy questions.

Artifacts are content-addressed release files. A contribution refers to an artifact by ID; the release index resolves the exact bytes. The host never imports an author's source tree at runtime.

Default Experience Suite

The package authoring brief declares:

• which mode is featured;
• the member-facing display order;
• one immutable default configuration for every mode;
• why each mode belongs in the Suite;
• which input options and creator surfaces are honestly supported.

Package defaults should make the intended experience work immediately. A member does not configure scoring rules or thresholds that would fragment progression. Advanced custom modes are a separate explicit workflow.

Exact public example

Manifest reference

The exact package schema is exported by @chasingmastery/contracts. Use the contract reference rather than copying a manifest from a different vertical and guessing which fields are meaningful.