Skip to content

spec: served city layout read, presence channel, run-trace activity stream - #723

Draft
Knucklessg1 wants to merge 1 commit into
mainfrom
city-served-rows
Draft

Knucklessg1 wants to merge 1 commit into
mainfrom
city-served-rows

Conversation

@Knucklessg1

Copy link
Copy Markdown
Member

What this change does

Three spec rows for the served city surface (follow-on from the arbora-city review on overstory PR #261):

  • ARBORA-FLEET-R084 — the fleet serves the city layout read: arbora serves the tenant's spatial layout from the Medulla world view (depends on MEDULLA-WORLD-VIEW-R003); no placement logic and no second registry in arbora. A connector added to the catalog appears on the next read without a write.
  • ARBORA-OPS-R915 — agent presence is served on one channel: a snapshot read with an explicit interval (default 5 s) and a bounded update rate; per-frame movement is never durable, interpolation is a presentation concern of the consumer.
  • ARBORA-OPS-R916 — the activity stream is served from run-trace provenance: cursor-paged run-trace step records; an event the engine has not recorded is not served, and arbora invents no activity.

Each row is wired into its spec trail (requirements, test-spec, tasks, spec.md functional requirement). Spec-only change: no code yet; the named tests are marked planned.

Sibling spec

MEDULLA-WORLD-VIEW (medulla, branch world-view-ontology) owns the spatial facts behind the layout read; MEDULLA-ORCH-VOCAB-R803 is the run-trace row the presence and activity reads serve from.

Verification

  • uvx pre-commit run --config .pre-commit-config.yaml --hook-stage pre-push spec --all-files → Passed
  • Commit-stage hooks (pre-commit --all-files, 14 hooks) → Passed

…race activity stream

Three spec rows for the city surface follow-on: the fleet serves the
spatial layout read from the Medulla world view (ARBORA-FLEET-R084, no
placement logic in arbora), agent presence is served on one channel with
an explicit snapshot interval and a bounded update rate
(ARBORA-OPS-R915, per-frame movement never durable), and the activity
stream is served from run-trace provenance (ARBORA-OPS-R916) so a
consumer can tell recorded engine activity from synthesized feeds.

Spec: none (spec rows for the served city surface; implementation is follow-on)
Co-Authored-By: Qwen 3.8-27B <noreply@qwen.ai>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant