AutoMovie API
    Preparing search index...

    Interface IAutoMovieDesignLineage

    Phases, alternatives, and derivation for one work, over identities other graphs own.

    Nothing here is a building. The record annotates ids that already exist elsewhere, which is what keeps a renovation from being modelled as a second building and an alternative from being modelled as a third. A production that declares no lineage at all is unaffected: this fold is additive, and its absence means only that no phase or alternative claim is being made.

    Explicit Engine lineage validators check coherence and supplied host identities. Production shot/build integration is retired; callers must invoke those checks and supply current graph identities rather than treating this record as automatic admission.

    interface IAutoMovieDesignLineage {
        decisions: IAutoMovieDesignDecision[];
        derived: IAutoMovieDerivedArtifact[];
        head: string;
        id: string;
        lifecycles: IAutoMovieDesignLifecycle[];
        phases: IAutoMovieDesignPhase[];
        revisions: IAutoMovieDesignRevision[];
        subjects: IAutoMovieDesignSubject[];
        variants: IAutoMovieDesignVariant[];
        version: 1;
    }
    Index

    Open and settled comparisons between those alternatives.

    Outputs computed from the identities above.

    head: string

    Revision the work is on now; every derived artifact must stamp it.

    id: string

    Stable, non-blank lineage identity within the production.

    Shared lineages should be canonically equal under one id; cross-shot consistency requires an explicit host after production merger retirement.

    Exactly one entry per declared subject.

    The construction plan, as an acyclic graph of prerequisites.

    Every recorded state of the authored source; at least one.

    Every identity this lineage speaks about.

    Alternatives preserved side by side over their base revisions.

    version: 1

    Schema version; validation accepts only 1.