Skip to content

Prism

Sight begins when a source survives the seeing.

An image can yield text, a crop, a depth estimate, or a reconstructed object, but each result must remain connected to the source it came from. Prism owns that visual and spatial grounding and transformation as an Aspect. It takes admitted sources through bounded operations and records their observations and derivatives. Captions, OCR, crops, reconstructions, conversions, and model judgments remain attributable results; none replaces the source.

Vision admission is Partial: current code preserves immutable ArtifactRef metadata, distinguishes vision from image-capable chat, and filters declarations by explicitly supplied required input modalities. No Prism package, byte-custody or materialization path, OCR tool, or visual provider ships today. State of Work owns that boundary; ADR 36 owns the designed contract.

Several faculties, one source

Choose the return needed by the consuming owner:

Return Passage
Text, regions, reading order, tables, or document derivatives Scanner.
Boxes, masks, depth, pose, flow, tracks, or registered change estimates Sight, with a separate Live Sight session for armed streams.
New or edited still-image candidates Image.
Generated or transformed moving-image candidates Video, including exact authorization and independent admission for native sound facets.
Geometry, appearance, parts, rigs, assemblies, or field representations Form; Voxel and block export follows bounded grids through schematic read-back.
Reusable motion curves, retargeted clips, or technical motion findings Kinesis, with Live Kinesis for bounded epoch-to-rig sessions.

A deployment chooses the faculties needed for that return and may combine them with precise workers, deterministic Prism Lens transforms, and an image-capable multimodal Mind. Each profile pins its exact implementation and supporting evidence. The Mind still supplies chat, and starting one service activates only its admitted faculties. Generation and editing require their own effects even when they consume grounded observations.

The optic path

admit source into custody
→ authorize materialization
→ inspect and decode
→ apply a declared transform
→ resolve an exact finite tool or dispatch an eligible provider
→ retain a grounded observation or derived artifact

The Reliquary must own source bytes before Prism acts. An ArtifactRef is immutable metadata, not byte custody or bearer authority; the designed materializer rechecks authority on every read. The source remains under its retention policy; see the artifact-reference boundary.

A deterministic transform produces a derived artifact recording parent and result digests, operation, immutable implementation revision, parameters, and declared loss. Provider request encodings and handles are transport forms, not universal storage or durable custody. Any retained visual output returns to artifact custody with provenance.

An observation must let its reader find the evidence again. It keeps the source and derivative chain, the relevant page, frame, time, or region, the requested task and output, and the producing provider or deterministic operation with its immutable revision. It also carries appropriate uncertainty and states whether the result is extraction, measurement, or inference.

Generated or edited media becomes a new artifact with effect provenance. A caption or OCR result can enter bounded Context, but that text is not the image; using it cannot silently replace or delete the source.

Designed interface register

These are semantic interfaces, not delivered source or claims that every provider implements every operation:

Interface and operation guide Domain request/result Execution binding
prism.image@2 ImageJob@2 and image artifacts/receipts Animator durable_job → JobGrant
prism.video@2 VideoJob@2 and video artifacts/receipts Animator durable_job → JobGrant
prism.sight@2 SightJob@2 / VisualObservationSet@1 Animator call/durable_job → matching grant; finite tool → Resolution Lock + ToolProfile
prism.form@2 FormJob@2 / FormAssetSet@1 Animator job → JobGrant; finite tool → Resolution Lock + ToolProfile
prism.kinesis@2 KinesisJob@2 / motion or findings set Animator job → JobGrant; finite tool → Resolution Lock + ToolProfile
prism.scanner@1: inspect, extract, OCR, structure Scanner request / DocumentObservation@1 Animator call/job → matching grant; direct tool → Resolution Lock + ToolProfile

Each leaf gives its operations and candidate dialect/driver studies.

The Designed-only prism.image@1, prism.video@1, prism.sight@1, prism.form@1, and prism.kinesis@1 interfaces and their corresponding *Job@1 request meanings remain historical. Revision 2 separates Prism technical result settlement from a consuming Composition's semantic adoption; Kinesis additionally replaces the former generic sonic-cue input with exact musical cue and clock contracts. No capability registry, domain job, or service attempt used the @1 designs, so there is no executable migration. prism.scanner@1 is unchanged.

ImageJob, VideoJob, SightJob, FormJob, and KinesisJob are domain work identities. Each asynchronous or durable provider or local execution is a separately identified ServiceJobAttempt@1. One domain job may receive another attempt only through declared forward-branch or retry law; the shared mechanics do not collapse these contracts into a generic MediaJob.

Choose execution according to who owns its lifecycle. A resident, shared, independently queued, or remote service is an Animator reached through CapabilityDemand@1 and a typed grant. For a finite library, CLI, or subprocess, the Spell Resolution Lock selects an immutable ToolProfile and a Worker delivers it into a trusted executor or Tomb. That finite tool needs no invented Animator or Rune.

Either path may use ServiceJobAttempt@1 when execution must survive the invoking Ghoul. A wrapper becomes an Animator only when it has the independent lifecycle, residency, queue, or remote boundary that warrants one.

Sight on finite iron

Prism uses ordinary Capabilities and Dispatcher routing. A local provider may be a managed Soulstone; a remote service remains an explicit Portal. For an otherwise eligible managed binding that is not WARM, Dispatcher returns HardwareTransitionRequired; the requesting Run enters Graph Stasis while Orchestrator converges readiness, then re-dispatches. The waiting transition carries no lease; Prism cannot revoke an issued lease or infer remote fallback from scarce local iron.

Designed Portal egress additionally requires eligible classification, explicit policy, consent where required, and a cost bound. Policy is evaluated on both the source and every derived artifact: a crop, caption, or normalized frame cannot launder restricted pixels.