Start here · MCP capability map
One customer journey, distinct MCP authorities
Choose the right connection for each task: author a project, inspect records, delegate work, build a processing plan or manage an environment. A tool on one server does not grant access to another.
Start here · MCP capability map
One customer journey, distinct MCP authorities
Choose the right connection for each task: author a project, inspect records, delegate work, build a processing plan or manage an environment. A tool on one server does not grant access to another.
What this view establishes
The architectural commitments
- A coding assistant can compose these surfaces, but credentials and authorization do not cross their boundaries. Discover each catalog before proposing a task.
- Ordinary code editing builds client applications over pinned contracts; there is no universal app-generation or arbitrary schema-authoring MCP tool.
- The next hosted proof should add Birdwatch and Field Notebook as isolated children on retained infrastructure, then prove sibling continuity through trim.
Layered platform stack
Project workspace
Project workspace
Initialize, verify grant, validate, bounded field edit, generate, package and plan. Local files and pinned artifacts; no cloud publication.
Repository authoring
Repository authoring
Read and propose schema/doc edits in a development checkout. Regeneration/checks turn proposals into reviewable diffs, not live schema changes.
Customer member data
Customer member data
Five reads; a live write delegation adds submit_mutation. Member ownership and agent attribution. Phase 4 locally proven; PR #49 merged.
Processing authority
Processing authority
Inspect graphs; plan/publish graphs and plan/apply bindings. Separate gateway credential. Available workers determine executable capabilities.
Deployment control
Deployment control
Inspect, plan, confirm create/trim and poll operations. Local shared-pool isolation proven; hosted pooling is the next acceptance target.
Main gateway
Main gateway
Schema, query, library, ordinary mutation, game resolve and processing catalog under gateway identity/access policy. Not customer delegation auth.
Tenant administration
Tenant administration
Future membership, roles and on-behalf-of issuance. No implicit admin powers, cross-member delegation or automatic renewal today.
What this view establishes
The architectural commitments
- A coding assistant can compose these surfaces, but credentials and authorization do not cross their boundaries. Discover each catalog before proposing a task.
- Ordinary code editing builds client applications over pinned contracts; there is no universal app-generation or arbitrary schema-authoring MCP tool.
- The next hosted proof should add Birdwatch and Field Notebook as isolated children on retained infrastructure, then prove sibling continuity through trim.
Follow the live system
Move from explanation to inspection
The Atlas is static and source-backed. The Observatory shows authenticated environment state.
7 repository sources behind this view
distribution/project-tools/src/neostory_project_tools/mcp.pydocs/customer-agent-journeys.mdgateway/src/neostory_gateway/agent_facade.pygateway/src/neostory_gateway/repo_bridge.pymcp/src/neostory_processing_mcp/server.pyplatform/customer-runtime/customer_runtime.pyplatform/deployment-mcp/src/neostory_deployment_mcp/server.py