Repository navigation
Direction section; generated release facts; byte-for-byte page check - #1
Merged
Merged
Conversation
…ons) A proposal for discussion, drafted from a review of every public roobli repository as of Noto v0.0.2-alpha.113 and @roobli/md v0.1.19: - direction/: the problem, the "edit the page, keep the file" positioning, audience, and the product line with a proposed stance per repository - principles: eight rules with a test and a current-state note each, plus a pass over the interface - roadmap: Now / Next / Later with gates, release tracks, and non-goals - open-source: the documentation and community-health standard and an audit of each repository against it - decisions: what is already decided, and twelve open questions Nothing here is decided until it is recorded under Decided. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_011Zsubk1jzejiCfkbLeWVQd
Direction: - D1 (repair Stable), D2 (the 0.1.0 gate) and D3 (0.1.0 as the first release outside alpha) move to Decided, with the private-material cleanup; statuses point at the pull requests that carry them. - New "Noto on the web" track (D13, D14): why the core is within reach, one core with two hosts, and phases W0 to W3. Site: - Download links and version facts come from GitHub Releases at build time (releases.data.ts, DownloadTiles, a /download page); the deploy runs every six hours so they follow releases without a commit. An unreachable API falls back to the releases list. - Every page must come back byte for byte from @roobli/md (scripts/roundtrip.mjs), checked on pull requests and before deploy. - The engine preview moves from @roobli/md v0.1.8 to v0.1.19. - New screenshots on a synthetic vault, with a language toggle. - The install guide stops promising archives and Intel builds releases do not carry. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_011Zsubk1jzejiCfkbLeWVQd
- The decision log records D4 to D14 as the owner decided them on 2026-09-29, and the history purge. Two items stay open: the Windows signing route once priced (D15) and the code of conduct contact (D16). - The Direction pages move from proposal to adopted, and links point at the decided entries. - D5: the home page leads with "Edit the page. Keep the file." - D10: LICENSE, CC BY 4.0 for prose and images, MIT for code; the footer says so. - The open-source audit reflects the merged organization defaults and the canvas and holt labels. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_011Zsubk1jzejiCfkbLeWVQd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging deploys to https://roobli.github.io/Noto.docs/ through the existing workflow. This is meant for paragraph-by-paragraph review, so comment inline anywhere.
Direction (
/direction/)A new section that records what Noto is trying to be, so each change can be checked against something other than momentum.
The web track (D13, D14) is new and rests on measured facts. The v3 Markdown pipeline touches Node in exactly one place (sha256). The editor never calls the desktop bridge. The work is therefore a host boundary, not a rewrite. The plan runs from W0 (below, in this PR) through W3, and nothing ships ahead of 0.1.0.
The site itself
/downloadpage. The deploy now also runs every six hours, so links follow releases without a commit, and an unreachable API falls back to the releases list. Today it resolves tov0.0.2-alpha.113and its four real downloads; before this it linkedalpha.30.scripts/roundtrip.mjsparses every page with@roobli/mdand serializes it with every block untouched, and the bytes must match. It runs on every pull request (newcheck.yml) and before every deploy. Today 14 pages pass. An invalid page was confirmed to fail it.@roobli/mdv0.1.8 to v0.1.19, the version Noto ships.Related
Verification
pnpm check:roundtrippasses: 14 pages come back byte for byte.pnpm docs:buildpasses, both with the Releases API reachable and with it unreachable (the fallback path).🤖 Generated with Claude Code
https://claude.ai/code/session_011Zsubk1jzejiCfkbLeWVQd
Generated by Claude Code