Rebuild the public site as a unified static-first knowledge system - #5
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 36b5b0844d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e95b04bcf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } catch { | ||
| return null; |
There was a problem hiding this comment.
When the org listing succeeds but a per-repo contents request fails for a repository that actually has .interdependency/project.yml (for example due to API rate limiting, a timeout, or invalid YAML), this catch makes that failure indistinguishable from “no manifest”. The rest of the run still has fallback === false, so the mapper publishes inferred frontier/hmmm fields and rewrites repos.last-known-good.json, erasing previously reviewed manifest metadata instead of falling back for that repo.
Useful? React with 👍 / 👎.
|
|
||
| const canon = JSON.parse(await readFile('src/_data/generated/canon.json', 'utf8')); | ||
| const repos = JSON.parse(await readFile('src/_data/generated/repos.json', 'utf8')); | ||
| if (canon.source.repository !== 'wayseer00/wayseer.github.io') throw new Error(`unexpected canon repository: ${canon.source.repository}`); |
There was a problem hiding this comment.
On a clean checkout, running the standalone package script npm run validate now fails at this new authority check because the committed src/_data/generated/canon.json in this commit still names The-Interdependency/a0 instead of the Wayseer source; I verified the script exits here before the refresh step that npm run build performs. Since validate remains a public script and this module declares it as an entrypoint, either commit matching generated data or make validation refresh/read the new provenance first.
Useful? React with 👍 / 👎.
| if (/^article\s+/i.test(title)) { | ||
| const count = (articleBySection.get(sectionId) || 0) + 1; | ||
| articleBySection.set(sectionId, count); | ||
| localId = `article-${count}`; |
There was a problem hiding this comment.
With the current canon, the nested heading ##### Article Two (low density) also matches this condition, so it consumes article-3 and shifts the real #### Article Three route/id to rights-and-definitions-of-the-way.article-4. Any inserted explanatory subheading that starts with “Article” will similarly renumber subsequent public URLs and unit IDs, so the counter should be limited to the canonical article level/pattern rather than every heading title prefix.
Useful? React with 👍 / 👎.
| let fallback = false; | ||
| let rawRepos = []; | ||
| let overrides = {}; | ||
| try { overrides = yaml.load(await readFile('src/_data/project-overrides.yml', 'utf8')) || {}; } catch {} |
There was a problem hiding this comment.
If src/_data/project-overrides.yml has a YAML typo or cannot be read, this empty catch silently replaces all reviewed central overrides with {}; when the GitHub repo listing then succeeds, the run is not marked as fallback and writes a new last-known-good snapshot with those reviewed summaries/statuses/purposes removed. Missing override files can still be optional, but parse/read errors for an existing reviewed file should fail the refresh rather than publish inferred metadata.
Useful? React with 👍 / 👎.
2 participants
What changed
wayseer00/wayseer.github.io:canon/the_interdependent_way.mdcanonical identity and visibly records remote versus recovery-mirror retrieval..interdependency/project.ymlmanifests or reviewed central overrides.artifacts/four-cuts-1.htmlat/artifacts/four-cuts/through the Eleventy deployment artifact._siteartifacts for 30 days before Pages deployment.Why
The repository contained an older hand-authored root site and a newer Eleventy scaffold with competing aesthetics and incomplete routing. The dynamic browser script queried an obsolete repository identity, canon provenance incorrectly named
a0, Article Lab pages did not contain parsed note text, and the Four Cuts artifact was not part of the generated deployment route system.This change makes static HTML the durable floor, moves dynamic discovery to build time, keeps canon and commentary distinct, and leaves uncertainty visible as
hmmminstead of manufacturing completion.Visitor and contributor impact
Visitors receive a calm orientation before dense source text, consistent status language, accessible progressive disclosure, repository constellation pages, and a complete no-JavaScript reading floor. Contributors receive an explicit
.interdependency/project.ymlcontract, offline build path, recovery workflow, bounded route rules, and generated-route tests.Validation — passing
GitHub Actions run
29315844817passed the full gate on head36b5b0844d03e3d9d8b8da5917f80eda813356cb:_siteroute checkshmmm