Align TGK references and supersede legacy notes
This commit is contained in:
parent
950a601fbe
commit
d8b30f268d
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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**.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s a textual/diagrammatic draft of the **overall architecture** for the unified ASL + TGK + PEL system with federation, SIMD/shard acceleration, and deterministic replay. I’ll describe the components and their connections clearly so it can later be converted to a visual diagram.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
NOTE: Superseded by tier1 TGK/1 and vendor/amduat/tier1/tgk-1-core.md; retained for historical context.
|
||||
|
||||
Absolutely — here’s 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.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -18,6 +18,8 @@ Tags: [deterministic, index, acceleration]
|
|||
|
||||
* `ASL-STORE-INDEX` — store lifecycle and replay contracts
|
||||
* `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:
|
||||
|
||||
* Artifact: `Reference`
|
||||
* TGK Edge: `CanonicalEdgeKey`
|
||||
* TGK Edge: canonical key defined by `TGK/1` and `TGK/1-CORE` (opaque here)
|
||||
|
||||
Properties:
|
||||
|
||||
|
|
@ -125,7 +127,7 @@ A Routing Key MAY incorporate:
|
|||
|
||||
* Hash of Canonical Key
|
||||
* 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
|
||||
|
||||
Absence of optional attributes MUST be encoded explicitly.
|
||||
|
|
@ -218,11 +220,11 @@ Rules:
|
|||
|
||||
### 8.2 TGK Edge Index
|
||||
|
||||
* Canonical Key: `CanonicalEdgeKey`
|
||||
* Canonical Key: defined by `TGK/1` and `TGK/1-CORE` (opaque here)
|
||||
* Routing Key components:
|
||||
|
||||
* `H(CanonicalEdgeKey)`
|
||||
* `edge_type_key`
|
||||
* `EdgeTypeId` (if present in the TGK profile)
|
||||
* Direction or role (optional)
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -22,6 +22,8 @@ It **does not define encoding** (see ENC-ASL-CORE-INDEX at `tier1/enc-asl-core-i
|
|||
**Informative references:**
|
||||
|
||||
* `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
|
||||
* Sharding or acceleration strategies (see ASL/INDEX-ACCEL/1)
|
||||
* Memory residency or caching
|
||||
* Federation or PEL semantics
|
||||
* Federation, PEL, or TGK semantics (see `TGK/1` and `TGK/1-CORE`)
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -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:
|
||||
|
||||
|
|
|
|||
|
|
@ -24,6 +24,7 @@ It does **not** define:
|
|||
* Index semantics (see ASL/1-CORE-INDEX)
|
||||
* Store lifecycle behavior (see ASL-STORE-INDEX)
|
||||
* 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)
|
||||
|
||||
---
|
||||
|
|
|
|||
Loading…
Reference in a new issue