stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
39359da17100e067d3c313392e34c11aaeff6d46
git.stella-ops.org/docs/implplan/AGENTS.md
StellaOps Bot 39359da171 consolidate the tests locations
2025-12-26 01:48:24 +02:00

2.9 KiB
Raw Blame History

AGENTS · docs/implplan (Coordination Sprints)

Purpose & Scope

  • Working directory: docs/implplan (sprint planning/coordination docs only). Cross-module edits must be explicitly noted in the relevant sprint’s Decisons & Risks.
  • Roles supported here: project manager, product manager, implementer (doc maintainer). No code changes are performed in this directory; focus on sprint plans, status, and cross-guild coordination.

Required Reading (treat as read before DOING)

  • docs/README.md
  • docs/07_HIGH_LEVEL_ARCHITECTURE.md
  • docs/modules/platform/architecture-overview.md
  • docs/implplan sprint template rules (see Section “Naming & Structure” below)
  • Any sprint-specific upstream docs linked from the current sprint file (e.g., crypto audit, replay runbooks, module architecture dossiers referenced in Dependencies/Prereqs sections)

Documentation Rules

  • Avoid external URLs unless already present; prefer relative doc links.

Advisory Handling (must do for every new advisory)

  • Trigger: any new/updated file in docs/product-advisories/ (current or archived) automatically requires updates below—no chat approval.
  • Docs: add/update a high-level page in docs/ (vision/key-features/market) and a detailed page in the closest area (docs/reachability/*, docs/market/*, docs/benchmarks/*, docs/modules/<module>/*, etc.). Inline only short snippets; place runnable/long code in docs/benchmarks/** or tests/** (deterministic, offline-friendly) and link.
  • Sprints: add Delivery Tracker rows in the relevant SPRINT_*.md, include doc paths, owners, deps; add an Execution Log line and risks/interlocks (schema/feed freeze, transparency caps) when needed.
  • De-dup: check docs/product-advisories/archived/; mark “supersedes/extends ` if overlapping to avoid duplicate tasks.
  • Defaults: hybrid reachability posture (graph DSSE required; edge-bundle optional), deterministic/frozen feeds, offline-ready benches.
  • Do not defer: execute steps immediately, then report.

Cross-Module Coordination

  • Respect each module’s AGENTS.md when touching module-specific sprint entries; do not change module instructions from here.
  • If a required module AGENTS.md is missing/outdated, mark the related task BLOCKED in that module’s sprint and note it in Decisions & Risks here.

Ready-to-Start Checklist (per change)

  • Confirm template compliance of the sprint file you’ll edit.
  • Verify statuses reflect current reality before adding new actions.
  • Add Execution Log line summarizing what changed, with date and role.

Testing / Validation

  • No automated tests; validate by: (1) template conformance, (2) table integrity (columns align), (3) links resolve locally.

Contacts & Stand-ups

  • Follow sprint-specific checkpoint dates listed in “Upcoming Checkpoints”. Escalations are logged in Decisions & Risks, not via chat.