docs(F1): three-node demo topology design (ADR 0012 + build spec)#150
Merged
Conversation
ADR 0012 + docs/three-node-demo-topology.md design the Phase F three-node Hugging Face demo: center (msk HQ) + two edge branches (spb/ekb) that push operational events over HTTPS, with stateless re-seed, sleep choreography, and the N1-N12 node invariants as the F2 test spec. Key decisions: this is the branch-distribution axis, deliberately distinct from the ADR 0010 multi-replica PostgreSQL scaling profile (the three nodes are separate single-replica Spaces with embedded control planes); HTTPS substitutes for the Kafka/Flink transport (semantics preserved); foreign branches (dxb/ala) stay narrative, not live nodes, to keep the "RU PII never crosses the border" governance claim honest; three Spaces under one liovina account, no second account or org needed (proven by existing live Spaces). architecture.md gets a parallel ADR callout. Design-only; F2 implements and the Space deploy is an owner gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
DORA Metrics
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
F1 — three-node demo topology (design)
Phase F of the endgame plan. Design-only: ADR 0012 + a build-contract spec + an
architecture.mdcallout. No code and no deploy — F2 implements, and the Space deploy is an owner gate.What this designs
A three-node public HF demo that shows the branch-distribution story live:
msk(HQ) — serving API in demo mode plus an authenticated node-ingest endpoint and a cross-branch view.spb+ekb— each seeds its branch slice and pushes operational events to the center over HTTPS.AGENTFLOW_NODE_*env; three Spaces under oneliovinaaccount (no second account / org).Key decisions (the irreversible calls — worth a look)
dxb/alastay narrative, not live nodes — keeps "RU PII never crosses the border" honest (no faux-PII over the public internet to a UAE/KZ Space).Files
docs/decisions/0012-three-node-demo-topology.md— the decision (context, options, honesty boundary, non-goals).docs/three-node-demo-topology.md— build contract for F2: Space/env matrices,POST /v1/node/eventscontract, canonical event payload, boot/emit/sleep sequences, deploy runbook, verify-live checklist, and N1–N12 node invariants as the test spec.docs/architecture.md— parallel ADR callout.Reuses the existing event path (
local_pipeline._process_event, the background generator, thepipeline_eventsjournal), so F2's new surface stays thin: an ingest endpoint + an edge emitter + a cross-branch view.🤖 Generated with Claude Code