← CRD inventorySource 1ea8b8ea8b01
Capability Requirements Document · derive-content-from-retained-source

Derive content from a retained source

Transform or analyze a governed source to produce a separately identifiable result with explicit provenance and processing state.

Status
draft
Version
0.1
Architecture alignment
compatible with constraints
Adoption
proposed
Known public realizations
none confirmed
Evidence basis
restricted assessment exists

Availability: unknown

Inventory note: In-place enrichment policy remains unresolved.

Core meaning

Capability purpose
Permit useful processing without losing source identity, integrity, or auditability.
Meaningful outcome
A derivative, or a durable failure/cancellation outcome, is linked to its source and processing request.
Boundaries — includes
operation request, authority check, processing state, derivative identity, source link, failure handling, and completion evidence.
Boundaries — excludes
initial retention, context allocation, retrieval policy, provider selection, and downstream use of the derivative.
Terms and concepts
derivative means a generated representation such as extracted text, summary, transcription, translation, classification, or conversion.

Interaction Contract MLEs

Produce a governed derivative

Actor
An authorized owner or governed processing workflow.
Command / intent
Apply a named transformation to a retained source.
Current state
The source exists and the requested operation is known.
Policies / invariants
Authority applies to the actual source; source identity remains intact; output provenance names source and operation; processing state is inspectable; retries do not create ambiguous success.
Transition
Record the request, process under policy, preserve the derivative's identity and source link, and record terminal state.
Result
A provenance-linked derivative or a reasoned failure/cancellation.
Events / effects
Status communications may be emitted; the derivative may become eligible for later capabilities.
Unknowns
Universal partial-result and human-correction semantics are not established.

Rules and defaults

Rules / invariants

Communication MLEs

Processing state changed

Purpose
Make meaningful processing progress or terminal state visible.
Trigger
Processing reaches a reportable state.
Audience
Owner or initiating actor.
Required meaning
Identify the source, operation, state, and any required action without implying success prematurely.
Representative example text
Example; illustrative, not shipped copy: “Processing completed and a linked result is available.”
Possible realizations
event, update feed, inline status, notification, or API result.

Unknown / unresolved

Statement provenance

StatementSemantic classEvidence statusSource / note
Source and derivative identities remain linked and distinct.rule/invariantsourcedPilot provenance P02.
Separate derivative output is preferred.recommended defaultsourcedHistorical design and current PIOS state treatment.
Canonical source ↗All CRDs