Prism

In plain words: Vision and media overview

Partial 4 min read 15 glossary terms 21 connected pages

The short version written for the Snayu team

The vision and media area (Prism) that takes admitted images, documents and video through bounded operations, OCR, detection, generation, 3D and motion, always linking results back to the exact source.

Why read it: Read this before adding any image, OCR, video, 3D or motion feature, to pick the right sub-area and execution path.

1Sub-areas: Scanner (documents), Sight, Image, Video, Form (3D), Kinesis (motion), plus live sessions.
2A caption or OCR text is a derived result, never a replacement for the source image.
3Today only image metadata and vision-vs-chat capability filtering exist; no Prism package or provider ships.

Partial Vision admission metadata only; no OCR, visual provider or byte custody.

Words on this page, decoded click one for its card

Where it sits in LychD

Vision & Media Prism

Seeing and generating images, video and 3D, always with the source kept separate from the result.

It's like: A photo lab.

Click a dot to open that part's card.

Glossary page In the network

In this section 9 pages

Sight Computer vision estimates The planned computer-vision path (Sight) for images and finite video, returning typed estimates such as boxes, masks, depth, pose, flow and tracks, each grounded to exact pixels and times. open → Live Sight Live camera sessions The planned bounded session for live camera or RTSP streams, defining arming, privacy masks, frame and clock tracking, gaps and reconnects, so old frames are never treated as current. open → Scanner Document OCR and extraction The planned document reading path (Scanner) that turns admitted PDFs, scans and photos into attributed text, regions, tables and reading order, with Markdown as just one output form. open → Image Image generation and editing The planned image-making path (Image) for generating, editing, inpainting, structure-controlled and enhancement jobs, recording the exact operation, inputs, profile and what changed. open → Video Video generation The planned video-making path (Video) for text-to-video, image-to-video and related temporal jobs, binding sources, prompts, controls and clocks, and returning technically validated candidate clips. open → Form 3D model generation The planned 3D path (Form) that turns photos, capture sets or existing meshes into validated 3D results, geometry, materials, rigs or fields, keeping source, scale and loss visible. open → Voxel and block export Voxel and Minecraft block export A planned 3D workflow that converts a model into a bounded voxel grid, maps it to a game block palette and exports a Sponge Schematic v3 (.schem) file, proving the result by reading it back. open → Kinesis Motion and animation processing The planned motion path (Kinesis) that turns pose estimates into reusable animation curves and handles motion generation, retargeting, cleanup, sync to music and validation, tied to exact clocks and rigs. open → Live Kinesis Live motion sessions The planned bounded session that streams motion from a live source, such as a camera or performance, to one target rig and consumer, exposing latency, gaps and stale output. open →

The original text Underlined words open their plain-English card.

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. PrismVision & Media owns that visual and spatial grounding and transformation as ana Extension DomainPlug-in Area. 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 PrismVision & Media 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 PrismVision & Media 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 ContextBriefing Pack, 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	AnimatorModel Runtime `durable_job` → `JobGrant`
`prism.video@2`	`VideoJob@2` and video artifacts/receipts	AnimatorModel Runtime `durable_job` → `JobGrant`
`prism.sight@2`	`SightJob@2` / `VisualObservationSet@1`	AnimatorModel Runtime `call`/`durable_job` → matching grant; finite tool → Resolution Lock + `ToolProfile`
`prism.form@2`	`FormJob@2` / `FormAssetSet@1`	AnimatorModel Runtime job → `JobGrant`; finite tool → Resolution Lock + `ToolProfile`
`prism.kinesis@2`	`KinesisJob@2` / motion or findings set	AnimatorModel Runtime job → `JobGrant`; finite tool → Resolution Lock + `ToolProfile`
`prism.scanner@1`: inspect, extract, OCR, structure	Scanner request / `DocumentObservation@1`	AnimatorModel Runtime 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 PrismVision & Media technical result settlement from a consuming CompositionApp'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 ana AnimatorModel Runtime reached through CapabilityDemand@1 and a typed grant. For a finite library, CLI, or subprocess, the SpellStep Resolution Lock selects an immutable ToolProfile and a Worker delivers it into a trusted executor or TombSandbox. That finite tool needs no invented AnimatorModel Runtime or RuneService Config File.

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

Sight on finite iron

PrismVision & Media uses ordinary Capabilities and Dispatcher routing. A local provider may be a managed SoulstoneLocal Model; a remote service remains an explicit Portal. For an otherwise eligible managed binding that is not WARM, DispatcherTraffic Controller returns HardwareTransitionRequired; the requesting RunJob Record enters GraphStep Map StasisPause while Orchestrator converges readiness, then re-dispatches. The waiting transition carries no lease; PrismVision & Media cannot revoke an issued lease or infer remote fallback from scarce local iron.

Designed PortalCloud Model 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.