Ask Daniel's CODEX

Grok Build Handoff — SynNA Master Phase Grid

Grok Build Handoff — SynNA Master Phase Grid

IN Lattice · Intelligent Netware · MA5 Council

Partnership model

Read this file for the ordered build grid. Gate history:

Architectural decisions (2026-06-18 evening — ratified by Daniel)

Gate 3 = Syd (Syndication proof)

Syd is primarily a proof form tab, with an optional light chat persona. Ratification = Approve for SQL button, not LLM sign-off.

Summary — when and who

Do not make Syd the default summary author — that adds persona tuning cost with no pipeline gain.

References block — footer, not body

• Source templates: assets/_Template7_Bottom_Sections_v1.html (and _Template2_v1.html, _Template3_v1.html, _Template5_Marketing_v1.html — <!-- REFERENCES BLOCK comment)
• Rendered by the NA module footer, stored as the REFERENCE DB field — not inside assembled.html body
• Static <li> list; only the syndication evidence <li> changes per article:

- https://scotomaville.com/syn-us?na={{NA_ID}} (or portal-specific variant) - [Portal:Keywords] token in link text where templates show it

• {{NA_ID}} = predicted next autoincrement → syn_config.yaml onboarding entry next_na_id: 238
• Bump next_na_id manually after each successful SSMS publish (until pyodbc helper exists)

Gate 3 UI

• Third sidebar card after Gate 1 (Imagery) and Gate 2 (Composition)
• Icon: fas fa-rss
• Tab id: syn-syd-proof
• Agent id: syd — added to agent_order.json after codey, before codex

Future — Lattice dashboard (post-Codex)

• Status board for all unpublished packets under pipeline_root
• Becomes default Lattice main area or second dashboard page mirroring left sidebar
• Build after Codex post-publish KB ingest is complete — not in Gate 3 scope

State machine (full)

`` drafted → masters_pending → images_pending → images_approved → assembled → proof_draft → proof_approved → sql_ready → published → archived ``

`na_record` block (Gate 3 packet contract)

Stored in status.yaml under na_record: (populated by assemble + Syd, edited in proof form):

```yaml na_record: title: ""

from SYN_PIPELINE; editable in proof

summary: ""

from Arnie SUMMARY; editable in proof

body_html_file: assembled.html

read-only pointer; not the DB references

references_html: ""

from template + {{NA_ID}}; editable in proof

categories: []

from Forrest brief; re-open cats picker

badge: ""

from Forrest brief

author_userid: 0

fixed from syn_config.publish.author_userid

author_display: ""

e.g. "Daniel Comp"

publish_at: ""

ISO

datetime; default now; future schedule OK expire_at: ""

optional; coupons/events

na_status: awaiting_approval

maps to NA module STATUS choices

na_id_reserved: 238

copied from syn_config.next_na_id at proof open

```

syn_config.yaml additions (Gate 3 onboarding)

``yaml publish: next_na_id: 238 author_userid: <fill> author_display: "Daniel Comp" references_template: "templates/syd/_references_li.html" syndication_url_pattern: "https://scotomaville.com/syn-us?na={na_id}" ``

Master phase grid

Rhythm every phase: backup → build → verify → update this handoff checkbox.

Backup convention: {file}_YYYYMMDD_HHMM.{ext} before touching app.py, index.html, syn_assemble.py, syn_pipeline.py.

PHASE 2

— Gate 2 completion (Codey) · before Gate 3

Exit criteria: Daniel signs off Codey preview for what-outlives-me before any Gate 3 work.

PHASE 3

— Arnie SUMMARY + references template · parallel-friendly after 2A

Exit criteria: Packet folder contains parseable summary; references HTML generates with na=238.

PHASE 4

— Gate 3 Syd proof shell · after 2D + 3E

Exit criteria: Proof tab auto-fills from what-outlives-me; all fields editable except author; references show na=238.

PHASE 5

— Syd approve + SQL build (2.6) · after 4I

Exit criteria: SSMS-ready SQL for what-outlives-me; state sql_ready.

PHASE 6

— Publish (3.1) · after 5E

Exit criteria: One article published; next_na_id incremented; packet archived.

PHASE 7

— Codex post-publish KB · after first publish

Exit criteria: Published article lands in KB without manual copy.

PHASE 8

— Lattice dashboard · after Phase 7

Exit criteria: Unpublished articles visible at a glance; no kanban required for v1.

Field map — legacy form → pipeline source

Verification quick reference

```bash cd D:\04_WORK\Code\Lattice\_ChatUI\.Scripts python syn_pipeline.py --test-assemble python syn_pipeline.py --test-sql-build

after 5C

```

```powershell

Gate 3 proof API (after 4D)

Invoke-RestMethod http://127.0.0.1:8780/api/pipeline/what-outlives-me/na-record

Server restart

$pid8780 = (netstat -ano | findstr ":8780.*LISTENING" | ForEach-Object { ($_ -split '\s+')[-1] } | Select-Object -First 1) if ($pid8780) { taskkill /PID $pid8780 /F } cd D:\04_WORK\Code\Lattice\_ChatUI; python app.py ```

Live packet: D:\03_MAP\Syn_Pipeline\what-outlives-me\

Daniel's decisions (2026-06-18 evening — ratified)

| Decision |

Shipped tonight (steps 3A + 2A)

• Arnie augmentation: required === SUMMARY === fence + Dachs SEO heuristics (app.py)
• syn_assemble.py: SUMMARY parse, dynamic markdown → Tahoe sections, status.summary
• Body templates simplified to {{ARTICLE_BODY}}
• Live packet what-outlives-me updated with full article + summary; reassembled
• syn_config.yaml: next_na_id: 239, operator userid map, references template path

Session continuity for Grok

1. Read this file for phase order
2. Read Gate 1/2 handoffs for regression context
3. Build one step ID per session (e.g. 3A, 4B) — no drive-by refactors
4. Backup before edit; verify before handoff update
5. Check off step in this file when milestone ships

Written by Grok Build · 2026-06-18 evening · Gate 3 Syd scoped · Master grid through dashboard.

Ask Daniel's CODEX