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

Start here · From field notes to a customer-owned application

From field notes to a customer-owned application

A six-scene customer story: review a domain, inspect its records, delegate a bounded task, build clients and choose an environment.

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

Start here · From field notes to a customer-owned application

From field notes to a customer-owned application

A six-scene customer story: review a domain, inspect its records, delegate a bounded task, build clients and choose an environment.

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 · Start with a real problem

    field-notebook-journey-1observed

    Start with a real problem

    An ecologist wants a private record of site visits, observations and places. The external Field Notebook project exists.

    On screenEli returns from a creek survey with paper notes. A simple record and place replace a spreadsheet row.

    Open the example LLM prompt
    Inspect the Field Notebook customer project, schema, namespace grant and release lock. Explain what its Record and Place model can express today. Propose only the smallest extension needed for creek surveys, and do not modify live records or fabricate a release pin.

    What you getA customer-owned project boundary; historical hosted proof is retained, but that pilot was shut down.

  2. 02
    01

    02 · Review before generating

    field-notebook-journey-2implemented

    Review before generating

    Project tools validate, generate, package and plan pinned artifacts. Generic product design still requires an implementation review.

    On screenThe assistant shows the schema diff and matching client types. Eli accepts the vocabulary before code generation.

    Open the example LLM prompt
    Discover the project tools. Validate this checkout and its namespace grant, then generate from the current project digest. Add an optional notes field only if the existing descriptor lacks it and the tool can express the exact change. Package against the verified generated inventory; show the resulting pins and remaining plan blockers.

    What you getA reproducible local artifact proposal. Packaging and project.plan do not publish or deploy it.

  3. 03
    01

    03 · Inspect the same record

    field-notebook-journey-3observed

    Inspect the same record

    The Observatory explains installed schema and records; the pilot proved Python, Swift and hydrated web against one record.

    On screenThree windows show the same record: Python creates, Swift changes its title, web reads the new revision. An inspector reveals ownership and history.

    Open the example LLM prompt
    In the selected local test environment, read the installed schema and a seeded record. Show its relationships, revision and ownership in the available inspection UI. Check that the client and inspector address the same authority. Do not call a generated schema snapshot live data.

    What you getA verified three-client historical example and a current local installed MCP proof; no current hosted endpoint is promised.

  4. 04
    01

    04 · Delegate a bounded task

    field-notebook-journey-4observed

    Delegate a bounded task

    Five reads become six tools only with a live write delegation. Human MCP access has ended; member HTTP access remains.

    On screenEli authorizes a notes assistant for a short duration. The agent writes; Eli reads the record as its owner, then revokes the assistant.

    Open the example LLM prompt
    Use the delegation configured privately in this environment. List tools, inspect the installed Record descriptor and propose a survey note. If submit_mutation is available and I approve the content, create it within my delegation bounds. Read it back and report the revision. After I revoke this delegation, verify the next write is refused without retrying under another credential.

    What you getThe local HTTPS/source-denied journey proves write, member read, restart replay and revocation. PR #49 is merged at bfb10b39. Hosted rollout is a separate acceptance.

  5. 05
    01

    05 · Build the clients

    field-notebook-journey-5implemented

    Build the clients

    Swift, Python and web candidates and a real external pilot exist. A prompt is a coding brief, not a universal app-generation MCP tool.

    On screenEli chooses a phone capture screen, web list and Python export. The assistant presents a UI diff and test results.

    Open the example LLM prompt
    Build a small web client and Swift capture screen in the customer repository using the pinned accepted packages, plus a Python read/export example. Include loading, empty, error and revoked-access states. Keep credentials server-side or in native secure storage. Show a hydrated browser proof and shared-record round trip; return a PR rather than deploying.

    What you getConcrete client implementation work over existing contracts. No promise of published packages or automatic production release.

  6. 06
    01

    06 · Choose a home and grow

    field-notebook-journey-6planned

    Choose a home and grow

    Dedicated hosting has historical proof; shared child create/trim has local isolation proof. Hosted pooling and operations remain follow-ups.

    On screenTwo environments appear under retained hosted infrastructure: Birdwatch and Field Notebook. Trimming a disposable child leaves its sibling and parent intact.

    Open the example LLM prompt
    Using deployment MCP, inspect my available project, recipes and environments, then plan a test environment for the verified release. Show isolation, target, capacity and revision. After explicit confirmation, create only an admitted environment. Before trimming it, re-read its generation and confirm the exact child; retain its parent and sibling. Report unavailable hosted recipes and recovery as blockers.

    What you getPrimary hosted follow-up: two isolated children on existing infrastructure, with provider-specific isolation and trim acceptance. No cloud resources are changed in this Atlas tranche.

The customer journey, step by step

01 · Start with a real problem02 · Review before generating03 · Inspect the same record04 · Delegate a bounded task05 · Build the clients06 · Choose a home and growStart with a real problem to Review before generating: Next reviewed step. declared.Start with a real problemReview before generating01 · Next reviewed stepdeclaredReview before generating to Inspect the same record: Next reviewed step. declared.Review before generatingInspect the same record02 · Next reviewed stepdeclaredInspect the same record to Delegate a bounded task: Next reviewed step. declared.Inspect the same recordDelegate a bounded task03 · Next reviewed stepdeclaredDelegate a bounded task to Build the clients: Next reviewed step. declared.Delegate a bounded taskBuild the clients04 · Next reviewed stepdeclaredBuild the clients to Choose a home and grow: Next reviewed step. declared.Build the clientsChoose a home and grow05 · 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

    Start with a real problemReview before generating

    Next reviewed step

    declared
  2. 02

    Review before generatingInspect the same record

    Next reviewed step

    declared
  3. 03

    Inspect the same recordDelegate a bounded task

    Next reviewed step

    declared
  4. 04

    Delegate a bounded taskBuild the clients

    Next reviewed step

    declared
  5. 05

    Build the clientsChoose a home and grow

    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

    Start with a real problemReview before generating

    Next reviewed step

    declared
  2. 02

    Review before generatingInspect the same record

    Next reviewed step

    declared
  3. 03

    Inspect the same recordDelegate a bounded task

    Next reviewed step

    declared
  4. 04

    Delegate a bounded taskBuild the clients

    Next reviewed step

    declared
  5. 05

    Build the clientsChoose a home and grow

    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.

11 repository sources behind this view
  • Explorer/app/shape.tsx
  • distribution/project-tools/src/neostory_project_tools/mcp.py
  • distribution/swift-client/tests/Notebook.swift
  • docs/customer-agent-journeys.md
  • docs/platform-business-cases.md
  • docs/releases/evidence/customer-data-mcp-phase4/runtime.json
  • docs/releases/evidence/records-v2-provider-readiness/hosted-three-client-receipt.json
  • gateway/src/neostory_gateway/delegation_repository.py
  • platform/customer-runtime/customer_runtime.py
  • platform/deployment-mcp/src/neostory_deployment_mcp/server.py
  • probes/platform-wave0/field-notebook/neostory.project.json