Skip to content

Stamp a trilogy pointer onto telos-md's set-north-star output#4

Open
dshanklin-bv wants to merge 1 commit into
mainfrom
fix/telos-trilogy-pointer
Open

Stamp a trilogy pointer onto telos-md's set-north-star output#4
dshanklin-bv wants to merge 1 commit into
mainfrom
fix/telos-trilogy-pointer

Conversation

@dshanklin-bv

Copy link
Copy Markdown
Contributor

Summary

  • eidos telos set-north-star writes .telos/config.yaml and a fresh north_stars/<id>.yaml with no mention that research.md → governor.md → docket.md exist, or where to find them.
  • telos-md itself deliberately holds zero sibling knowledge (see telos.md's .converge/telos-holds-zero-sibling-knowledge-eidos-owns-the-ecosystem-map.md — a tested decision that cross-forge knowledge belongs to eidos, not duplicated into every forge).
  • So this wraps set-north-star at the eidos-cli layer instead: a small surgical override that calls the same underlying telos_md._logic.loop.set_north_star, then prepends a trilogy-pointer comment block to both files it writes. telos-md's own source is untouched.

Test plan

  • Full suite run against this branch: 69 passed, 5 pre-existing failures (zoltar/skills-hub/doctor/closeout/ship — all environment-dependent plugin-discovery checks), reproduced identically on main with none of this change applied.
  • ruff check / ruff format --check clean on both touched files.
  • Manually verified: reminder present in both config.yaml and north_star.yaml, JSON output/warnings unaffected, idempotent on rerun (checked via marker string before prepending).

🤖 Generated with Claude Code

telos-md deliberately holds zero sibling knowledge as of its own
"eidos owns the map" refactor -- so this lives here instead. Wraps
set-north-star (the only command that writes config.yaml + a fresh
north_star.yaml) to prepend a comment block naming research.md ->
governor.md -> docket.md and linking their docs, without telos-md
itself ever importing or referencing those tools.

Verified against a real repo: warnings unaffected, JSON output
unchanged, reminder present in both files, idempotent on rerun. The
5 pre-existing test failures on main (zoltar/skills-hub/doctor/
closeout/ship, all environment-dependent plugin-discovery checks)
are unrelated -- reproduced identically on main without this change.
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