Align TGK references and supersede legacy notes

This commit is contained in:
Carl Niklas Rydberg 2026-01-17 07:37:47 +01:00
parent 950a601fbe
commit d8b30f268d
13 changed files with 41 additions and 6 deletions

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a **formal draft of C structures** for the unified execution plan, mapping operators, parameters, and the DAG serialization format. This aligns with the **ENC-ASL-TGK-INDEX** model and preserves deterministic snapshot semantics. Absolutely — heres a **formal draft of C structures** for the unified execution plan, mapping operators, parameters, and the DAG serialization format. This aligns with the **ENC-ASL-TGK-INDEX** model and preserves deterministic snapshot semantics.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a **formal draft of operator pseudocode** for the unified ASL + TGK execution plan. This pseudocode captures **shard/SIMD acceleration, deterministic execution, snapshot safety, and DAG traversal**, mapping directly to ENC-ASL-TGK-INDEX. Absolutely — heres a **formal draft of operator pseudocode** for the unified ASL + TGK execution plan. This pseudocode captures **shard/SIMD acceleration, deterministic execution, snapshot safety, and DAG traversal**, mapping directly to ENC-ASL-TGK-INDEX.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a **formal draft for integrating PEL deterministic DAG programs with the ASL + TGK execution plan**, including how PEL outputs feed into operators, while preserving snapshot safety, determinism, and memory efficiency. Absolutely — heres a **formal draft for integrating PEL deterministic DAG programs with the ASL + TGK execution plan**, including how PEL outputs feed into operators, while preserving snapshot safety, determinism, and memory efficiency.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a formal draft for **runtime execution semantics and memory layout** for SIMD/shard acceleration of the unified execution plan over ENC-ASL-TGK-INDEX. This focuses on **parallel, deterministic, and snapshot-safe execution**. Absolutely — heres a formal draft for **runtime execution semantics and memory layout** for SIMD/shard acceleration of the unified execution plan over ENC-ASL-TGK-INDEX. This focuses on **parallel, deterministic, and snapshot-safe execution**.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a textual/diagrammatic draft of the **overall architecture** for the unified ASL + TGK + PEL system with federation, SIMD/shard acceleration, and deterministic replay. Ill describe the components and their connections clearly so it can later be converted to a visual diagram. Absolutely — heres a textual/diagrammatic draft of the **overall architecture** for the unified ASL + TGK + PEL system with federation, SIMD/shard acceleration, and deterministic replay. Ill describe the components and their connections clearly so it can later be converted to a visual diagram.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
# Unified ASL + TGK + PEL System Specification (Master Reference) # Unified ASL + TGK + PEL System Specification (Master Reference)
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Heres a **formal draft of the execution plan specification** for the unified ASL + TGK query execution model. It defines operators, data flow, and snapshot semantics in a deterministic, layered way. Heres a **formal draft of the execution plan specification** for the unified ASL + TGK query execution model. It defines operators, data flow, and snapshot semantics in a deterministic, layered way.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a **draft for a unified query execution model** over the merged ENC-ASL-TGK-INDEX. It treats ASL artifacts and TGK edges uniformly for queries, respects snapshots, and preserves determinism. Absolutely — heres a **draft for a unified query execution model** over the merged ENC-ASL-TGK-INDEX. It treats ASL artifacts and TGK edges uniformly for queries, respects snapshots, and preserves determinism.
--- ---

View file

@ -1,3 +1,5 @@
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
Absolutely — heres a formal draft of **C structure mappings and binary encoding** for artifacts, PERs, TGK edges, shards, and execution plans in the unified ASL + TGK + PEL system. This is meant for **C libraries, API frontends, and toolchains**, preserving memory alignment, determinism, and snapshot safety. Absolutely — heres a formal draft of **C structure mappings and binary encoding** for artifacts, PERs, TGK edges, shards, and execution plans in the unified ASL + TGK + PEL system. This is meant for **C libraries, API frontends, and toolchains**, preserving memory alignment, determinism, and snapshot safety.
--- ---

View file

@ -18,6 +18,8 @@ Tags: [deterministic, index, acceleration]
* `ASL-STORE-INDEX` — store lifecycle and replay contracts * `ASL-STORE-INDEX` — store lifecycle and replay contracts
* `ENC-ASL-CORE-INDEX` — bytes-on-disk encoding profile (`tier1/enc-asl-core-index.md`) * `ENC-ASL-CORE-INDEX` — bytes-on-disk encoding profile (`tier1/enc-asl-core-index.md`)
* `TGK/1` — TGK semantics and visibility alignment
* `TGK/1-CORE` — EdgeBody and EdgeTypeId definitions
--- ---
@ -69,7 +71,7 @@ The **Canonical Key** uniquely identifies an indexable entity.
Examples: Examples:
* Artifact: `Reference` * Artifact: `Reference`
* TGK Edge: `CanonicalEdgeKey` * TGK Edge: canonical key defined by `TGK/1` and `TGK/1-CORE` (opaque here)
Properties: Properties:
@ -125,7 +127,7 @@ A Routing Key MAY incorporate:
* Hash of Canonical Key * Hash of Canonical Key
* Artifact type tag (if present) * Artifact type tag (if present)
* TGK edge type key * TGK `EdgeTypeId` or other immutable classification attributes (TGK/1-CORE)
* Direction, role, or other immutable classification attributes * Direction, role, or other immutable classification attributes
Absence of optional attributes MUST be encoded explicitly. Absence of optional attributes MUST be encoded explicitly.
@ -218,11 +220,11 @@ Rules:
### 8.2 TGK Edge Index ### 8.2 TGK Edge Index
* Canonical Key: `CanonicalEdgeKey` * Canonical Key: defined by `TGK/1` and `TGK/1-CORE` (opaque here)
* Routing Key components: * Routing Key components:
* `H(CanonicalEdgeKey)` * `H(CanonicalEdgeKey)`
* `edge_type_key` * `EdgeTypeId` (if present in the TGK profile)
* Direction or role (optional) * Direction or role (optional)
--- ---

View file

@ -22,6 +22,8 @@ It **does not define encoding** (see ENC-ASL-CORE-INDEX at `tier1/enc-asl-core-i
**Informative references:** **Informative references:**
* `ASL/SYSTEM/1` — unified system view (PEL/TGK/federation alignment) * `ASL/SYSTEM/1` — unified system view (PEL/TGK/federation alignment)
* `TGK/1` — TGK semantics and visibility alignment
* `TGK/1-CORE` — EdgeBody and EdgeTypeId definitions
--- ---
@ -40,7 +42,7 @@ Excludes:
* Disk-level encoding * Disk-level encoding
* Sharding or acceleration strategies (see ASL/INDEX-ACCEL/1) * Sharding or acceleration strategies (see ASL/INDEX-ACCEL/1)
* Memory residency or caching * Memory residency or caching
* Federation or PEL semantics * Federation, PEL, or TGK semantics (see `TGK/1` and `TGK/1-CORE`)
--- ---

View file

@ -148,7 +148,19 @@ The index is the shared substrate:
--- ---
## 8. Summary ## 8. Glossary and Terminology Alignment (Informative)
To prevent drift across layers, the following terms map as:
* **EdgeBody** (`TGK/1-CORE`) — logical edge content (`from[]`, `to[]`, `payload`, `type`).
* **EdgeArtifact** (`TGK/1-CORE`) — ASL Artifact whose payload encodes an EdgeBody.
* **EdgeRef** (`TGK/1-CORE`) — ASL Reference to an EdgeArtifact.
* **TGK index record** (`TGK/1`, `ASL/1-CORE-INDEX`) — index entry that makes an EdgeRef visible under snapshot/log rules; contains no edge payload.
* **TGK traversal result** (`TGK/1`) — snapshot/log-bounded set of visible edges (EdgeRefs) and/or node references derived from indexed EdgeArtifacts.
---
## 9. Summary
ASL/SYSTEM/1 provides a single, consistent view: ASL/SYSTEM/1 provides a single, consistent view:

View file

@ -24,6 +24,7 @@ It does **not** define:
* Index semantics (see ASL/1-CORE-INDEX) * Index semantics (see ASL/1-CORE-INDEX)
* Store lifecycle behavior (see ASL-STORE-INDEX) * Store lifecycle behavior (see ASL-STORE-INDEX)
* Acceleration semantics (see ASL/INDEX-ACCEL/1) * Acceleration semantics (see ASL/INDEX-ACCEL/1)
* TGK edge semantics or encodings (see `TGK/1` and `TGK/1-CORE`)
* Federation semantics (see federation/domain policy layers) * Federation semantics (see federation/domain policy layers)
--- ---