ContriveAtlas
neostory-schema-set/22snapshot a59c206cec9d
Open Observatory

Start here · From a sighting to a personal field guide

From a sighting to a personal field guide

A six-scene customer story: reuse a real Bird domain, build a local notebook, then separate scoped-agent and recognition possibilities from installed capability.

Customers · Product builders · Operators
DeclaredImplementedObservedPlanned
neostory-schema-set/22snapshot a59c206cec9d

Start here · From a sighting to a personal field guide

From a sighting to a personal field guide

A six-scene customer story: reuse a real Bird domain, build a local notebook, then separate scoped-agent and recognition possibilities from installed capability.

Customers · Product builders · Operators6 nodes · 5 directed relationships

What this view establishes

The architectural commitments

  1. Prompts are task briefs for an MCP-capable coding assistant, not a guarantee that every LLM can run every tool. Discover the connected tool catalog first.
  2. Implemented means source exists; observed names a specific proof. Birdwatch has no hosted gateway; the retired Field Notebook pilot is not a live service.
  3. Customer write admission is in PR #49 merged at bfb10b39. Processing, deployment and tenant administration are different authority surfaces.

Customer storyboard

  1. 01
    01

    01 · Choose what matters

    birdwatching-journey-1implemented

    Choose what matters

    BirdDomain represents sightings, species and certainty. The current native entry form defaults new sightings to Confirmed; richer uncertainty editing is a next client improvement.

    On screenMaya pauses beside a marsh. The frame moves from binoculars to a sighting card: date, count, certainty and notes.

    Open the example LLM prompt
    I want a personal birdwatching notebook. Inspect the existing BirdDomain schema first. Show me how BirdObservation, BirdSpecies and observationIdentifiesSpecies preserve uncertainty. Propose missing concepts separately; do not invent descriptor IDs or change the schema yet.

    What you getAn existing domain inventory, followed by a small, reviewable schema proposal.

  2. 02
    01

    02 · Shape the domain

    birdwatching-journey-2implemented

    Shape the domain

    Repository schema proposals and generation exist. Arbitrary external-domain authoring is still a coding workflow.

    On screenA split screen shows the natural-language request beside a schema diff, then generated Swift/Python/web contracts.

    Open the example LLM prompt
    In an isolated customer repository, inspect the available project and schema tools. Reuse the granted namespace and pinned package dependencies. Model sightings and species from the reviewed design, validate and generate, then show the diff. If a tool supports only an optional string field, report that limit and use a reviewed code edit for anything broader.

    What you getA validated proposal, not an automatically published schema. No namespace or release permission is invented.

  3. 03
    01

    03 · Use the notebook

    birdwatching-journey-3implemented

    Use the notebook

    Birdwatch has native entry, library, SQLite storage and shared inspection components. Its hosted front door is unconfigured.

    On screenMaya saves an observation, then opens the library and follows its species relationship. Local storage is labeled on screen.

    Open the example LLM prompt
    Build the existing Birdwatch macOS app for a disposable local demonstration. Keep it disconnected from production. Show observation entry, the saved record and its relationships. Preserve the source app defaults and report whether the demo used local storage or a verified authority.

    What you getA native local app. Customer-runtime MCP acceptance for this Bird schema is a separate installation task.

  4. 04
    01

    04 · Ask an assistant to help

    birdwatching-journey-4planned

    Ask an assistant to help

    The customer framework has scoped reads and locally proven write admission; a Bird runtime needs its own schema closure and acceptance.

    On screenMaya approves a short-lived assistant. The screen separates the proposed note from the member-owned saved record.

    Open the example LLM prompt
    Once this Bird environment is accepted, use my privately configured delegation. Inspect tools/list and schema descriptors. Find my possible sightings from today and propose clearer notes without upgrading certainty. With a write delegation, apply only the approved note edits; then show the resulting member-owned records and attribution.

    What you getField Notebook proves the authority mechanism. Bird-specific installation, MCP journey and hosted acceptance remain to be done.

  5. 05
    01

    05 · Add assisted identification

    birdwatching-journey-5planned

    Add assisted identification

    Processing graph plan/publish and bindings exist on the processing gateway; no bird recognizer is shipped by this story.

    On screenAudio flows into a proposed recognizer, then candidate species and confidence, then a human review checkpoint.

    Open the example LLM prompt
    On a gateway that exposes processing tools, inspect its catalog. Draft a Source/Map/Sink graph for audio-to-candidate-species only if an installed worker supports it. Otherwise list the missing worker and evidence contract. Keep candidate identifications separate from confirmed sightings; do not publish or activate the graph without reviewing the exact plan.

    What you getA graph proposal and an explicit missing-worker list. Customer MCP has no processing tools or media-resource writes.

  6. 06
    01

    06 · Grow into a field guide

    birdwatching-journey-6planned

    Grow into a field guide

    A shared birding club, offline media sync and administrative delegation need further product and operational acceptance.

    On screenA phone, browser and club map share a visual language. Private sightings remain distinct from approved shared observations.

    Open the example LLM prompt
    Design a Birdwatch web companion and a native capture flow using the pinned client contracts. Preserve Possible, Probable and Confirmed. Separate private notes from a proposed club-sharing workflow. Produce a client PR and tests; list missing hosting, media sync, cross-member sharing and tenant-admin capabilities instead of simulating them as live.

    What you getClient code can be authored now; club sharing and fully hosted end-to-end automation remain explicit follow-ups.

The customer journey, step by step

01 · Choose what matters02 · Shape the domain03 · Use the notebook04 · Ask an assistant to help05 · Add assisted identification06 · Grow into a field guideChoose what matters to Shape the domain: Next reviewed step. declared.Choose what mattersShape the domain01 · Next reviewed stepdeclaredShape the domain to Use the notebook: Next reviewed step. declared.Shape the domainUse the notebook02 · Next reviewed stepdeclaredUse the notebook to Ask an assistant to help: Next reviewed step. declared.Use the notebookAsk an assistant to help03 · Next reviewed stepdeclaredAsk an assistant to help to Add assisted identification: Next reviewed step. declared.Ask an assistant to helpAdd assisted identification04 · Next reviewed stepdeclaredAdd assisted identification to Grow into a field guide: Next reviewed step. declared.Add assisted identificationGrow into a field guide05 · Next reviewed stepdeclared

Connections and evidence

Open the 5-relationship source key

Numbers set an explanatory reading order. They do not measure runtime timing.

  1. 01

    Choose what mattersShape the domain

    Next reviewed step

    declared
  2. 02

    Shape the domainUse the notebook

    Next reviewed step

    declared
  3. 03

    Use the notebookAsk an assistant to help

    Next reviewed step

    declared
  4. 04

    Ask an assistant to helpAdd assisted identification

    Next reviewed step

    declared
  5. 05

    Add assisted identificationGrow into a field guide

    Next reviewed step

    declared

Connections and evidence

5 directed, source-backed relationships

Numbers set an explanatory reading order. They do not measure runtime timing.

  1. 01

    Choose what mattersShape the domain

    Next reviewed step

    declared
  2. 02

    Shape the domainUse the notebook

    Next reviewed step

    declared
  3. 03

    Use the notebookAsk an assistant to help

    Next reviewed step

    declared
  4. 04

    Ask an assistant to helpAdd assisted identification

    Next reviewed step

    declared
  5. 05

    Add assisted identificationGrow into a field guide

    Next reviewed step

    declared

What this view establishes

The architectural commitments

  1. Prompts are task briefs for an MCP-capable coding assistant, not a guarantee that every LLM can run every tool. Discover the connected tool catalog first.
  2. Implemented means source exists; observed names a specific proof. Birdwatch has no hosted gateway; the retired Field Notebook pilot is not a live service.
  3. Customer write admission is in PR #49 merged at bfb10b39. Processing, deployment and tenant administration are different authority surfaces.

Follow the live system

The Atlas is static and source-backed. The Observatory shows authenticated environment state.

9 repository sources behind this view
  • distribution/project-tools/src/neostory_project_tools/mcp.py
  • docs/customer-agent-journeys.md
  • docs/platform-business-cases.md
  • docs/releases/evidence/customer-data-mcp-phase4/runtime.json
  • domains/bird/Apps/Birdwatch/Sources/BirdwatchAppModel.swift
  • domains/bird/Apps/Birdwatch/Sources/BirdwatchRootView.swift
  • domains/bird/schema/bird-domain.schema-package.json
  • mcp/src/neostory_processing_mcp/server.py
  • platform/customer-runtime/customer_runtime.py