coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/.claude/rules/repo-boundary.md
tegwick e7f615be38
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
docs: realign WP-0029 and boundaries with canon and nexus owners 
Review ACTIVITY-WP-0029 against info-tech-canon, policy-nexus, and
State Hub retirement: activity-core keeps schedule and ops_run;
repo-manager owns consistency; hub-core owns progress ports.
Mark WP-0026 finished. Refresh INTENT, SCOPE, and repo-boundary.
2026-08-18 10:27:29 +02:00

1.1 KiB
Raw Blame History

Repo boundary

This repo owns activity-core only: when / what / where — schedules, ActivityDefinitions, rule/instruction evaluation, ops_run claim queue, and bounded declared side-effects.

It does not own:

  • Task / work-item vocabulary → info-tech-canon (Task Model)
  • Responsibility / accountability / org roles → info-tech-canon (Organization Model)
  • Policy content (canon, ADRs) → owning repo files
  • Policy publication → policy-nexus (policy.coulomb.social)
  • Regulatory intake / interpretation → risk-nexus
  • Repo registry, C-rule consistency, work-record index → repo-manager
  • Messages, progress projections, hub ports → hub-core
  • Temporary compatibility routes → state-hub until STATE-WP-0079 retirement
  • Issue lifecycle / external tracker mapping → issue-core
  • AuthN / directory → key-cape / identity
  • AuthZ decisions → flex-auth
  • SSH certificates → ops-warden (warden sign only)
  • Secrets / API keys → OpenBao (railiance-platform); route via warden route
  • Tunnels → ops-bridge
  • Domain work execution → per-repo workers / rein-aharness claiming ops_runs