Compilation, review, and lifecycle

Creator source, compiled artifacts, and release authority are separate. The current authoring CLI implements the middle compilation step for a local owner-synthetic preview; it does not turn source into an approved release.

阅读中文版

Artifact layers

Creator Source Package
        │ deterministic compile
        ▼
Canonical Authoring IR
        │ deterministic lowering
        ▼
RuntimeBundleContent
        │ external evidence and release process
        ▼
ReleaseEnvelope / eligible activation

Layer	Owner and purpose	Current authoring command
Creator Source Package	Human-readable Creator meaning, provenance, and bounded dramatic space	Reads this input
Canonical Authoring IR	Compiler-normalized IDs, typed semantics, policy constraints, and provenance	Emits canonical-authoring-ir.json
RuntimeBundleContent	Immutable, content-addressed executable content for the generalized harness	Emits runtime-bundle-content.json plus declared assets
ReleaseEnvelope	External rights, consent, Creator/asset approval, runtime configuration, qualification, scope, expiry, revocation, quarantine, and activation evidence bound to exact artifacts	Not created or modified by this CLI

This separation is an accepted product boundary. It prevents editable Creator YAML from approving itself and prevents a bundle digest from being mistaken for rights or publication authority.

What compile does

The command:

uv run --project apps/api meet-u-compile-pilot \
  --content-root content \
  --output-root /tmp/meet-u-my-pilot-bundles \
  --package-id my-pilot \
  --version 1

performs a deterministic full-package build for local_owner_synthetic_preview. It:

• safely resolves the package, six modules, and declared assets;
• validates the closed field contracts and the cross-file semantic graph;
• reads the package default locale from the current platform presentation catalog;
• binds source, compiler, platform-policy, canonicalization, options, and module-closure identities;
• lowers canonical Authoring IR and immutable runtime bundle content; and
• writes a directory named by the runtime bundle SHA-256 digest.

The output includes different per-run UUIDs in the compile result, but identical effective inputs produce the same canonical IR and runtime-bundle content bytes and digests.

The CLI also accepts two advanced identity flags:

• --source-ref defaults to the canonical repo://content/creator-sources/<package-id>/v<version> form. The compiler rejects any noncanonical override, so most authors should omit it.
• --idempotency-key accepts a UUID for compile-command lineage. When omitted, the CLI creates a fresh UUID. It does not change deterministic IR or bundle content identity.

The compiler does not call an LLM. Future AI assistance may help draft source, but production-affecting generated material must become frozen, human-reviewed, provenance-linked Creator source before compilation.

What --check proves

After an ordinary compile, repeat the command with --check. The CLI compiles into a temporary directory and compares every expected directory/file and file digest with the existing content-addressed output.

A passing check proves reproducibility for those exact effective inputs and the continued presence of the expected output. It does not compare creative quality, run model behavior evaluations, inspect rights, or confer lifecycle status.

What a successful result does not prove

The current compiler deliberately returns activatable: false. Even when status is succeeded, the result does not prove:

• ownership, adaptation rights, contributor consent, voice/likeness consent, or intended-use permission;
• Creator approval of character portrayal, canon, exact copy, or dramatic space;
• approval of the exact portrait and outcome assets;
• model/runtime-configuration qualification against acceptance evidence;
• eligibility for a tester, consumer, public, or production scope;
• publication, activation, expiry, revocation, or rollback state; or
• authorization to use real user messages or private relationship history.

Do not add any of those claims to source-package.yaml. Lifecycle and provider fields are intentionally forbidden throughout Creator source.

Practical states for the current workflow

These labels describe how collaborators should communicate; they are not new YAML fields:

State	Honest claim
Draft source	Human meaning is still being authored and references may be incomplete
Structurally valid source	The loader accepts the seven-file graph and asset closure
Compiled candidate	The current compiler emitted deterministic IR/bundle content; activatable remains false
Creatively reviewed candidate	A human Creator reviewed the package meaning and relevant output; the compile result itself does not record this
Behaviorally evaluated candidate	Separate evaluation evidence covers the exact source/bundle/configuration under the stated scope
Release-eligible artifact	External rights, approvals, configuration, qualification, and policy evidence bind the exact artifact for a scope
Active release	A separate authorized activation operation selected that eligible release

Only the first three are directly addressed by this documentation and CLI. The broader states describe the accepted architecture, not a claim that a general production release workflow exists today.

Current local owner-preview boundary

The accepted owner-preview direction prioritizes one understandable local story loop and removes repeated per-change evidence/activation ceremony from the internal proof of concept. The current application has reached ordinary conversation, a minimal turn trace, and two manual owner checkpoints. The first commits a bounded character decision, deterministic outcome, and wait state; the second publishes a validated proactive return, one package-approved static outcome visual, a structured Journal, and a public-safe causal timeline. This does not add ambient scheduling, external notification, or live image generation. The lighter process does not collapse artifact layers, activate an arbitrary compiled package, or authorize a public release.

The accepted current scope remains local development with authorized synthetic input. It does not authorize tester, consumer, public, remote, or third-party data, production delivery, training use, live image generation, or external proactive notifications. A broader audience requires a new accepted decision and the controls appropriate to that scope.

Versioning source responsibly

During drafting, fix fields and references within the task worktree and rerun the compiler. Once a source version has been reviewed or used as the input to bound evidence, treat its package/version path and bytes as frozen. Changing source bytes changes source and module-closure digests even when an ID remains the same, so prior approval, qualification, or release evidence cannot silently cover the change.

Creator Source Package v1 does not yet define a complete author-facing version policy: it does not settle which changes increment a module content_version, which require a new package.version, how corrections, rollback, revocation, and migration are represented, or how bilingual copy is bound to one semantic version. Until that policy is accepted, do not invent a permanent rule. For reviewed or evidence-bound material, use a new source version as the conservative handoff and ask the product/decision owner to confirm the scope and review target.

Do not edit generated canonical IR or runtime-bundle content by hand. They are derived artifacts. Fix the Creator source or the compiler, then rebuild and review the semantic and digest changes.

Handoff checklist

Before calling a package a compiled candidate:

• review the human dramatic brief and the complete seven-file source diff;
• confirm all provenance references describe real source authority without claiming approval they do not carry;
• compile from the intended content root;
• run the same build with --check;
• inspect that status is succeeded and activatable is false;
• record the source version and emitted source, module-closure, IR, bundle, compiler, policy, and options identities when reproducibility matters;
• review the English or Chinese default-locale surfaces actually selected;
• keep the output inside local synthetic scope; and
• state separately what human review or evaluation has and has not occurred.

For field syntax return to the v1 field reference; for creative authority return to the semantic guide.