coordination
canonical-hours
experimental · public- the question
- How can scattered agent activity become one board that survives a restart?
- the primitive
- a status board that polls on a schedule
- record
- A standing agent and MCP surface that folds GitHub, Linear, lectio, and snapshot observations into an operational board.
position
declared dependencies how →
- artifactagentic-research/mache releasescanonical-hours/Taskfile.yml
- library@agentic-research/dpop 0.3.0canonical-hours/package.json
Declared, but not asserted. A source names something these repositories are not observed to publish under that name, so the target was identified by matching a name against a convention — true today, and able to go quietly wrong on a rename. Listed rather than dropped, and deliberately excluded from the statements above and from graph.json's edges.
- tenancycanonical-hours → cloister — declares _meta."art.cloister/v1"canonical-hours/server.json — a namespaced _meta key whose owner is identified by a constant in this generator
- artifactcanonical-hours → mache — machecanonical-hours/.mache-version — a `.<tool>-version` filename, where the tool name comes from the FILENAME rather than from anything the target declares