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

Engines · Processing engine

Immutable processing intent becomes durable work with inspectable provenance

Processing graphs declare what should happen; a compiler pins the exact revision and capability closure; durable queues and leases decide where it runs; ordinary graph records preserve the run, node outputs, artifacts, and review lineage.

Product · Engineering · Operations
DeclaredImplementedObservedPlanned
neostory-schema-set/22snapshot a59c206cec9d

Engines · Processing engine

Immutable processing intent becomes durable work with inspectable provenance

Processing graphs declare what should happen; a compiler pins the exact revision and capability closure; durable queues and leases decide where it runs; ordinary graph records preserve the run, node outputs, artifacts, and review lineage.

Product · Engineering · Operations11 nodes · 11 directed relationships

What this view establishes

The architectural commitments

  1. Graph definitions, immutable revisions, execution plans, and runtime capabilities are distinct contracts with distinct lifecycles.
  2. A queue or lease coordinates execution; it never becomes the semantic record of what happened.
  3. Every admitted output remains traceable to an exact run, node, implementation, input, and artifact policy.

Intent, execution and provenance layers

04

Published intent

graph-definitiondeclared

Graph definition

Reusable nodes, ports and semantic purpose

graph-revisionimplemented

Graph revision

Immutable topology, configuration and contract hash

trigger-bindingimplemented

Trigger binding

Application intent selects a published revision

compilerimplemented

Pure compiler

Validates topology and builds a deterministic plan

04

Work and capabilities

dispatchimplemented

Dispatch policy

Routes work by capability, origin and artifact policy

durable-workimplemented

Durable work queue

Restart-safe intent, claims, retries and leases

local-capabilityimplemented

Native capability

On-device media and trusted local processors

server-capabilityimplemented

Server capability

Leased worker operations over the same plan

03

Durable provenance

processing-runimplemented

Run and node records

Lifecycle, implementation version and exact inputs

artifactsimplemented

Artifact bindings

Content-addressed outputs with producer lineage

review-evidenceimplemented

Reviewable evidence

Signals and proposals remain inspectable before use

Connections and evidence

Open the 11-relationship source key

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

  1. 01

    Graph definitionGraph revision

    publishes

    implemented
  2. 02

    Graph revisionPure compiler

    pins

    implemented
  3. 03

    Trigger bindingDispatch policy

    requests

    implemented
  4. 04

    Pure compilerDispatch policy

    portable plan

    implemented
  5. 05

    Dispatch policyDurable work queue

    queues

    implemented
  6. 06

    Durable work queueNative capability

    claims locally

    implemented
  7. 07

    Durable work queueServer capability

    leases remotely

    implemented
  8. 08

    Native capabilityRun and node records

    records

    implemented
  9. 09

    Server capabilityRun and node records

    reports

    implemented
  10. 10

    Run and node recordsArtifact bindings

    binds outputs

    implemented
  11. 11

    Artifact bindingsReviewable evidence

    supports

    implemented

Connections and evidence

11 directed, source-backed relationships

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

  1. 01

    Graph definitionGraph revision

    publishes

    implemented
  2. 02

    Graph revisionPure compiler

    pins

    implemented
  3. 03

    Trigger bindingDispatch policy

    requests

    implemented
  4. 04

    Pure compilerDispatch policy

    portable plan

    implemented
  5. 05

    Dispatch policyDurable work queue

    queues

    implemented
  6. 06

    Durable work queueNative capability

    claims locally

    implemented
  7. 07

    Durable work queueServer capability

    leases remotely

    implemented
  8. 08

    Native capabilityRun and node records

    records

    implemented
  9. 09

    Server capabilityRun and node records

    reports

    implemented
  10. 10

    Run and node recordsArtifact bindings

    binds outputs

    implemented
  11. 11

    Artifact bindingsReviewable evidence

    supports

    implemented

What this view establishes

The architectural commitments

  1. Graph definitions, immutable revisions, execution plans, and runtime capabilities are distinct contracts with distinct lifecycles.
  2. A queue or lease coordinates execution; it never becomes the semantic record of what happened.
  3. Every admitted output remains traceable to an exact run, node, implementation, input, and artifact policy.

Follow the live system

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

21 repository sources behind this view
  • Explorer/app/processing/VideoProcessingEvidenceDashboard.tsx
  • Explorer/app/processing/videoEvidence.ts
  • Sources/MediaProcessing/ManualProcessingBindingAuthority.swift
  • Sources/MediaProcessing/MediaRuntimeCapabilityBridge.swift
  • Sources/MediaProcessing/SignalArtifactPersistence.swift
  • Sources/NeoStoryProcessing/ProcessingArtifactPolicy.swift
  • Sources/NeoStoryProcessing/ProcessingCatalog.swift
  • Sources/NeoStoryProcessing/ProcessingDispatch.swift
  • Sources/NeoStoryProcessing/ProcessingManualDispatch.swift
  • Sources/NeoStoryProcessing/ProcessingRuntime.swift
  • Sources/NeoStoryProcessing/ProcessingWork.swift
  • Sources/NeoStoryProcessing/ProcessingWorkRouter.swift
  • Sources/NeoStorySQLite/SQLiteProcessingQueue.swift
  • Sources/ProcessingDomain/ProcessingDomain.swift
  • Sources/ProcessingDomainRuntime/ProcessingRunObservability.swift
  • docs/processing-graph-foundation.md
  • docs/swift-processing-runtime.md
  • docs/v3-measurement-workbench.md
  • gateway/src/neostory_gateway/processing_work.py
  • schema/processing-domain.schema-package.json
  • worker/README.md