Skip to content

feat: add /methodology/ page — published specification address - #82

Merged
transitrix merged 1 commit into
mainfrom
transitrix-site/541-methodology-page
Sep 2, 2026
Merged

transitrix merged 1 commit into
mainfrom
transitrix-site/541-methodology-page

Conversation

@transitrix

Copy link
Copy Markdown
Owner

Summary

  • New /methodology/ page serves as the canonical address for the Transitrix methodology specification
  • Version is fetched from GitHub Releases at runtime (no hand-maintained versions)
  • Page explains versioning, stability, and how to read the full specification
  • Positioning language from transitrix-hq#423 (verbatim, committed copy below)
  • Updated what-can-i-model to link to /methodology/ instead of GitHub
  • CI check validates page links to latest methodology release

What the page carries

Pointer with state: The page names the current version and links to the full specification. It does not restate the specification — that lives in the published release.

Current version at runtime: JavaScript fetches the latest transitrix/methodology release from GitHub and updates the page. A hand-maintained version number would be wrong from the next release onward, so this automation is how it stays current.

Acceptance checklist

  • Page at https://transitrix.com/methodology/ returns 200 (local test)
  • Page names the current methodology release (v5.0.0 as of 2026-09-02)
  • Page links to full specification on GitHub
  • Page explains semver and migration recipes
  • Positioning language is verbatim from transitrix-hq#423
  • Sitemap includes /methodology/ (regenerated via generate_sitemap.py)
  • Page is reachable from existing page (what-can-i-model now links to it)
  • CI fails when page is out-of-sync with latest release (methodology-version-check.yml)

Positioning statement (transitrix-hq#423)

"You leave with a decision you can keep true. Not a report of one — the model the decision was made in, in your own repository, and the method to keep it current after we are gone. That is what Architecture-as-Code for the enterprise is for: the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach."

The page uses the category form (permitted short form per transitrix-hq#423):

"Architecture-as-Code for the enterprise — the git-native, text-first discipline software already has, carried up to the strategy, business and architecture layers that code-scoped tools never reach."

Testing

Manual test: fetch latest v5.0.0 from transitrix/methodology, confirm page displays version and links correctly.
CI check will fail on the next methodology release if the page isn't updated; this validates the automation.


From: transitrix-site.

Closes transitrix-hq#541

- New /methodology/ page serves as the canonical address for the Transitrix
  methodology specification
- Page fetches current version from GitHub Releases at runtime; no hand-maintained
  version numbers
- Specification pointer includes: current version, semver stability, migration
  recipes for majors, link to full specification on GitHub
- Positioning language from transitrix-hq#423 (verbatim)
- CI check (methodology-version-check.yml) fails if page is out-of-sync with
  latest methodology release
- Updated what-can-i-model to link to /methodology/ instead of GitHub
- Regenerated sitemap to include /methodology/ (via generate_sitemap.py)

Closes transitrix-hq#541

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@transitrix
transitrix merged commit f0e2d01 into main Sep 2, 2026
8 checks passed
@transitrix
transitrix deleted the transitrix-site/541-methodology-page branch September 2, 2026 18:19
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