Add the badge and the maturity disclaimer #16

2026-08-10T20:45:48-07:00

dejima-agent commented

2026-08-10 20:45:48 -07:00

Summary generated by LLM agent

Two independent additions, peeled out of #15 so they can merge without waiting on the review that one needs.

The badge

The same asset and markup dejima carries, placed where dejima places it: at the end of the opening block, before the first section heading.

The maturity disclaimer

From dejima #117. Its wording covers all three repositories by name — "these projects", "any of these repositories" — so a reader landing here would never have seen it.

Duplicated rather than linked, which is the opposite of what attribution and the security policy do here. That is deliberate. A disclaimer behind a link is a disclaimer the reader does not see, and its whole value is being on the page where the security argument is being made. Everything else that gets linked is reference material someone goes looking for; this is the one thing that has to arrive uninvited.

test/disclaimer.bats pins it. The line is the one most likely to be dropped without anyone deciding to drop it — by a rewrite of some section that happened to contain it — and every other test here would still pass on a repository that had lost it.

That is not theoretical. Writing the same guard on the sister project, a git checkout README.md during verification reverted the paragraph from the index and I committed the branch without the thing it existed to add. The guard failed on the next run.

What is deliberately not here

docs/threat-model.md does not exist on main yet — it arrives in #15 — so the disclaimer's third location and the corresponding line in this test come with it. #15 is stacked on this branch and extends the test's file list by one entry.

The widened image test that would catch a broken badge reference is also in #15, for the same reason: test/links.bats arrives there.

Verified

bats test/ passes, 88 ok and 0 failed.

**Summary generated by LLM agent** Two independent additions, peeled out of #15 so they can merge without waiting on the review that one needs. ## The badge The same asset and markup dejima carries, placed where dejima places it: at the end of the opening block, before the first section heading. ## The maturity disclaimer From dejima #117. Its wording covers all three repositories by name — "these projects", "any of these repositories" — so a reader landing here would never have seen it. **Duplicated rather than linked, which is the opposite of what attribution and the security policy do here.** That is deliberate. A disclaimer behind a link is a disclaimer the reader does not see, and its whole value is being on the page where the security argument is being made. Everything else that gets linked is reference material someone goes looking for; this is the one thing that has to arrive uninvited. `test/disclaimer.bats` pins it. The line is the one most likely to be dropped without anyone deciding to drop it — by a rewrite of some section that happened to contain it — and every other test here would still pass on a repository that had lost it. That is not theoretical. Writing the same guard on the sister project, a `git checkout README.md` during verification reverted the paragraph from the index and I committed the branch without the thing it existed to add. The guard failed on the next run. ## What is deliberately not here `docs/threat-model.md` does not exist on `main` yet — it arrives in #15 — so the disclaimer's third location and the corresponding line in this test come with it. #15 is stacked on this branch and extends the test's file list by one entry. The widened image test that would catch a broken badge reference is also in #15, for the same reason: `test/links.bats` arrives there. ## Verified `bats test/` passes, 88 ok and 0 failed.

dejima-agent added 2 commits 2026-08-10 20:45:49 -07:00

Add the Developed in dejima badge 3b95ff7a30

The same asset and markup dejima carries, placed where dejima places it: at the end of the opening block, before the first section heading.

Pin the maturity disclaimer on every entry point

tests / runner-env (confined) (pull_request_target) Successful in 1m40s

Details

tests / tests (pull_request_target) Successful in 2m8s

Details

tests / compose-schema (pull_request_target) Successful in 1m50s

Details

tests / runner-env (privileged) (pull_request_target) Successful in 1m37s

Details

c61eebb5b5

dejima carries this and its wording covers all three repositories by name: these projects, any of these repositories. A reader landing here would not have seen it.

Duplicated rather than linked, which is the opposite of what attribution and the security policy do here, and deliberately. A disclaimer behind a link is a disclaimer the reader does not see, and its whole value is being on the page where the security argument is being made. Everything else that gets linked is reference material someone goes looking for; this is the one thing that has to arrive uninvited.

test/disclaimer.bats pins it. The line is the one most likely to be dropped without anyone deciding to drop it - by a rewrite of some section that happened to contain it - and every other test here would still pass on a repository that had lost it.

dejima-agent referenced this pull request

2026-08-10 20:48:04 -07:00

Bring across what the sister project grew, and write down the threat model #15

branderson approved these changes 2026-08-10 21:04:14 -07:00

branderson merged commit 4cb86b4bdd into main

2026-08-10 21:04:20 -07:00

branderson referenced this issue from a commit

2026-08-10 21:04:22 -07:00

Merge pull request 'Add the badge and the maturity disclaimer' (#16) from disclaimer-and-badge into main

Sign in to join this conversation.