1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

/* method-ASK_activation-lifecycle-comparison.source.js
   D05 // activation and lifecycle comparison // source-v1 // 2026-07-28

   Subject: five artifact forms and their DISTINCT activation and lineage models. They are NOT
   one carrier family — a grounding note is a context artifact and a PTX is a provenance
   artifact; only some members here are intent carriers.
   The figure exists to stop one inheritance error: every carrier type inheriting the
   routed-instance filename lifecycle because they share a plane. The orthogonal terminal
   -TBI overlay may still sit above other eligible artifacts without entering that lifecycle.

   A canonical vN lineage is not a routed-instance lifecycle. A deployment is not an
   invocation. An ingestion is not a disposition.

   Repo prose is source of truth: docs/intent-artifacts.md, docs/source-of-intent.md. */

window.TREE_D05 = {
  kind: 'root',
  label: 'ACTIVATION + LIFECYCLE',
  note: 'five artifact forms · five different models — none inherits another’s',
  children: [
    { kind: 'section', label: 'grounding note', tag: 'standing context canonical', children: [
      { label: 'lineage', note: 'canonical vN · frozen _vN snapshots in the historical plane' },
      { label: 'activation', note: 'STANDING — a required read; no invocation event, no deployment act' },
      { label: 'force', note: 'normative context. May carry durable intent limbs without becoming an intent carrier' },
      { label: 'NOT', note: 'not a routed instance. Reading or feeding it creates no routed-instance filename state, and its fixed-path canonical is never renamed merely to record that it was read' },
    ]},
    { kind: 'section', label: 'Project Instructions', tag: 'standing operative carrier', children: [
      { label: 'lineage', note: 'canonical vN + snapshots' },
      { label: 'activation', note: 'DEPLOYED — ASK installs the payload into a live field; the field is a deployment mirror verified against the canonical' },
      { label: 'drift check', note: 'the live field and the canonical are compared; a canonical revision does not by itself repaste the field' },
      { label: 'NOT', note: 'a canonical filename change is not a lifecycle event' },
    ]},
    { kind: 'section', label: 'prompt', tag: 'invocable operative carrier', children: [
      { label: 'lineage', note: 'canonical vN + snapshots — the canonical FILENAME is unchanged by use' },
      { label: 'activation', note: 'INVOKED — ASK selects it and relays or feeds it; the invocation produces a result, not a state change on the carrier' },
      { label: 'NOT', note: 'invocation leaves no suffix. A prompt does not become -ingested' },
    ]},
    { kind: 'section', label: 'routed handoff', tag: 'the ONLY routed-instance filename lifecycle', children: [
      { label: '1 · routed', note: 'origin makes it durably available at the recipient intake · terminal -TBI = ASK still owes a feed' },
      { label: '2 · fed', note: 'ASK hands it to the recipient’s active surface — by value or by exact path' },
      { label: '3 · ingested', note: 'the recipient reads it into active context · -TBI becomes -ingested · disposition still OPEN' },
      { label: '4 · disposition', note: 'terminal rename + durable record in ONE bounded operation · absorbed / held / declined / withdrawn / routed / no-route / closed / supersededP' },
      { label: 'pre-ingestion exit', note: '-supersededA — retired before ingestion, never consumed' },
    ]},
    { kind: 'section', label: 'PTX', tag: 'provenance artifact', children: [
      { label: 'lineage', note: 'the PTX files ARE the lineage · optional _vN indexes the transcript artifact · no canonical-plus-snapshot chain' },
      { label: 'creation', note: 'ASK ASSEMBLES the multi-thread projection — capture, not activation' },
      { label: 'activation', note: 'read as evidence, or later FED under a new relay envelope' },
      { label: 'later feed', note: 'a PTX MAY carry terminal -TBI. Feeding it creates a NEW relay whose envelope governs how it is read — it does not make the transcript a handoff' },
      { label: 'NOT', note: 'not an authority converter · quoting a statement inside a PTX does not make that statement operative' },
    ]},
  ],
};