Skip to content

docs: add ECOSYSTEM.md, the works-with page - #4

Open
Chheng64 wants to merge 1 commit into
mainfrom
docs/ecosystem-page
Open

docs: add ECOSYSTEM.md, the works-with page#4
Chheng64 wants to merge 1 commit into
mainfrom
docs/ecosystem-page

Conversation

@Chheng64

@Chheng64 Chheng64 commented Aug 7, 2026

Copy link
Copy Markdown
Owner

What

ECOSYSTEM.md — what "works with your existing workflow" means, stated structurally rather than as a partner list. Plus a README docs-table row and a CHANGELOG entry.

Why this shape

  • Every artifact is markdown, HTML, JSON or CSV on disk; every check is a zero-dependency Node script with an exit code. Anything that reads a file or runs a command can participate — that claim carries the page, and each category backs itself with an existing document (FAQ.md, VALIDATION_ENGINE.md, ARTIFACT_FLOW.md, DIFFERENTIATORS.md, checks.yml).
  • A Future connectors section quarantines the planned items — the dtk CLI, the shared artifact store, the Phase 5 packs — each row linking its PUBLIC_ROADMAP.md phase, so the line between "works today" and "planned" stays visible.
  • Named ECOSYSTEM.md rather than INTEGRATIONS.md: the page is about compatibility, not built-in connectors. The toolkit ships none; that is the point, not a gap.

Validation

  • node tools/linkcheck.mjs — 952/952 internal links resolve, exit 0
  • node tools/mermaidcheck.mjs — 34 blocks, 0 findings, exit 0

🤖 Generated with Claude Code

Compatibility stated structurally — open artifacts and exit codes —
with planned connectors quarantined in their own section, each row
linking its roadmap phase. Named for compatibility, not connectors:
the toolkit ships none, and that is the point.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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