chore: register repository governance baseline
Some checks failed
tamq-ci / test (push) Failing after 6s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc
This commit is contained in:
tegwick 2026-08-24 14:16:11 +02:00
parent 7c76f79463
commit 7b4a972655
18 changed files with 902 additions and 0 deletions

View file

@ -0,0 +1,65 @@
---
id: TAMQ-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: communication
repo: tmux-amq
status: finished
owner: codex
topic_slug: coulomb-social
created: "2026-08-24"
updated: "2026-08-24"
---
# Bootstrap State Hub integration
Local durable message queue and tmux endpoint runtime for coordinating agent workers across gita-registered repositories.
## Review Generated Integration Files
```task
id: TAMQ-WP-0001-T01
status: done
priority: high
```
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
Completed during registration: purpose, boundaries, classification, State Hub
identity, credential routing, and repository-specific instructions were
reviewed and made concrete.
## Verify Local Developer Workflow
```task
id: TAMQ-WP-0001-T02
status: done
priority: high
```
Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.
Completed with the uv, pytest, Makefile check, compilation, and CLI smoke
commands recorded in `AGENTS.md` and `.claude/rules/stack-and-commands.md`.
## Seed First Real Workplan
```task
id: TAMQ-WP-0001-T03
status: done
priority: medium
```
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run the sync locally from this repo
checkout:
```bash
statehub fix-consistency
```
Completed by creating `TAMQ-WP-0002`, which owns the explicitly deferred
coordination-engine adapter boundary.

View file

@ -0,0 +1,53 @@
---
id: TAMQ-WP-0002
type: workplan
title: "Coordination-engine adapter boundary"
domain: communication
repo: tmux-amq
status: backlog
owner: codex
topic_slug: coulomb-social
created: "2026-08-24"
updated: "2026-08-24"
---
# Coordination-engine adapter boundary
Connect coordination-engine to tmux-amq through the existing local Unix-socket
boundary while preserving tmux-amq's local transport authority and keeping
workflow/orchestration policy in coordination-engine.
## Specify the adapter contract
```task
id: TAMQ-WP-0002-T01
status: todo
priority: high
```
Define request, response, identity, delivery, acknowledgement, retry, and
failure semantics for a coordination-engine client. Resolve protocol-version
negotiation and document which system owns each state transition.
## Implement the coordination-engine client adapter
```task
id: TAMQ-WP-0002-T02
status: wait
priority: high
```
Implement the adapter against the stable socket contract without importing
tmux/control-mode concerns into coordination-engine. This task waits for T01.
## Prove interoperability and recovery
```task
id: TAMQ-WP-0002-T03
status: wait
priority: high
```
Add end-to-end coverage for delivery, acknowledgement, reconnect, replay,
deduplication, incompatible protocol versions, and endpoint disappearance.
Update both repositories' operator documentation with the verified workflow.