* RFC-0040: A shared list of checked names, and names in GitHub text
Updates RFC-0029. Adds standards/feature-names.md, the suite-wide list of
names checked under RFC-0029, seeded with RFC-0029's examples and the
PhotoCraft inventory from #43, and says how the rule applies to issue,
pull request and commit text.
* RFC-0029: add PhotoCraft's names to the examples table instead of a new RFC
Drops RFC-0040 and standards/feature-names.md. The rows only show how the
existing rule applies, so they don't change RFC-0029's meaning (RFC-0013,
point 4).
* Add standards/naming.md: RFC-0029 in short form, with the names list
A file each repository's AGENTS.md can link, like standards/time.md.
Moves the PhotoCraft rows out of RFC-0029's table into it; RFC-0029 gets
only a pointer.
* naming.md: suggest our names for the open rows, explain the unchecked list
* naming.md: restore RFC-0029's descriptive-words sentences, use the existing naming doc, drop 'proposed'
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* naming.md: record the rule 4 check for the suggested names
Owner list and US register checked on 2026-11-16. Cloud Library, Pin Warp,
Paragraph Composer and Line Composer replaced or dropped; WIPO still open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Adopt the shared compatible-dependency allowlist and unmodified MPL-2.0 terms. The owner decision and promised strict-core/community/shared-library follow-up are recorded in the PR discussion.
Original RFC by @FredApps.
* Add RFC-0023: A web runtime for the Craft apps
* RFC-0023: split joined clauses
* RFC-0023: link the draft PR
* Update references after the 0024/0025 renumber
* RFC-0023: acceptance requirements for flush semantics, budget caps, worker ownership
* Split joined clauses
* RFC-0023: drop unverifiable production claims per review
* Add RFC-0021: An e-signature contract for the suite
* RFC-0021: add non-normative reference implementations
* RFC-0021: link the draft PR
* RFC-0021: lifecycle and evidence guarantees per review
* Update references after the 0024/0025 renumber
* RFC-0021: settle the consumers, PdfCraft and WordCraft named, pipeline stated
* Split a joined clause
* RFC-0014: Accessibility in every UI chang
* RFC-0014: manual tests never block; platform checks; owner, RFC-0007
- A screen-reader test is never a condition for merging. The
needs screen reader test label is for accessibility fixes and for
accessibility logic an app builds itself, not for every UI PR.
- CI reads the running app through the platform's accessibility API
with standard tools (UI Automation on Windows), so contributors never
install a screen reader.
- The kittest requirement doesn't block review until the shared helpers
exist.
- Owner and review check (CodeRabbit path instructions), and how the
priority rule sits on RFC-0007's levels.
* RFC-0014: the rules in standards/, the AGENTS.md text as its own block
craftrules is retired, so the rules are standards/accessibility.md here,
which also answers the first open question. The appendix becomes
standards/house-rules-accessibility.md, a generated block like the Rust
rules, because the core block has no room for it. Point 10 says where each
part goes and what the house-rules check needs. The README lists both files.
An accepted RFC isn't edited: a later RFC changes it, with Updates: or
Obsoletes: under its title as IETF RFCs do, and the old one gets an
Updated by: or Obsoleted by: back-link. Fixes that don't change the
meaning are ordinary PRs. An RFC can name a living document for the
current rules. Updates RFC-0000, which gets its back-link here.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add RFC-0020: Live collaboration: presence, invites, chat, concurrent text
* RFC-0020: name the session contract with scope locks in the landing order
* RFC-0020: add non-normative reference implementations
* RFC-0020: chat hosting modes, the web aside and the native internal surface
* RFC-0020: both chat hosting forms are options on web and native alike
* RFC-0020: conformance guarantees for mixed editing and invite redemption
* RFC-0020: split joined clauses
* Update references after the 0024/0025 renumber
* RFC-0020: engine decision, snapshot pairing, reopen and reconnect cases, recoverable drops, FigCraft relationship
* Split joined clauses
* RFC-0020 make craft-crdt conditional on the oracle in the landing order
Landing-order step 2 presumed craft-crdt as the text layer while the oracle that would qualify it arrived a step later. The contracts PR now lands first, carrying the differential text oracle, independent of accepting any engine. The craft-crdt PR is conditional on passing that oracle against the chosen library, with the mature-library route staying the default. The reference section stays non-normative as marked.
* Add RFC-0019: Suite accounts and tokens
* RFC-0019: add non-normative reference implementations
* RFC-0019: cross-app lifecycle guarantees per review
* Renumber to RFC-0025, resolving the 0019 collision with #34
* Fix a joined clause in the renumber note
* RFC-0025: refresh is wholly flow-owned, out of this RFC
* Split joined clauses in the refresh scope note
* RFC-0025: link the extraction draft PR
* RFC-0025: explain the suite folder and keychain names, offer the rename
* Split a joined clause
* RFC-0025: converge on one secret store, monotonic generations across re-add
* Split a joined clause
* RFC-0025: credentials are identity infrastructure, AI is one consumer
* RFC-0025 state the secrecy rule as backend conformance, never an absolute
The no-token-in-any-file wording contradicted the encrypted-file fallback the same text requires. The rule now forbids plaintext secrets in any suite-written file and names the encrypted fallback as the one permitted on-disk form, holding ciphertext only. Both halves are conformance requirements on the token store backend with tests on the extraction PR. The interface never promises what only a storage backend does, the same split the storage track uses for conflict handling.
* Add RFC-0001: Cloud documents across the suite
* RFC-0018: renumber from 0001, add architectural boundaries from review
* RFC-0018: add non-normative reference implementations
* RFC-0018: name the git adapter and ranged reads in the contract
* RFC-0018: link the draft part PRs and the keychain RFC
* RFC-0018: conflict handling as per-adapter acceptance tests
* RFC-0018: serial list fix
* RFC-0018: precondition enforcement is provider behavior, never interface-decidable
* Renumber to RFC-0024, resolving the 0018 collision with #30
* RFC-0024: link the suite-account draft PR
* RFC-0024: adapter fixes named as part of the move, bridge step, optional hosted jobs
* RFC-0024 name the two conflict strengths and tie each to the provider's protocol
The strict exactly-one-succeeds test and the local adapter's permitted check-then-write contradicted each other. The guarantee now comes in two named strengths. Atomic refusal binds every adapter whose protocol defines a conditional write, per HTTP conditional requests. Serialized refusal binds adapters over protocols with no such primitive, asserting the stale-save refusal and documenting the window. The provider's protocol decides which strength applies, so the interface never demands more than the standard the provider speaks.
* RFC-0003: Claiming issues
* docs: distinguish active drafts from unstarted claims
Address the review requests to retain the 24-hour window for comment-only, unstarted claims and use a friendly check-in for active drafts rather than automatic expiry. Preserve existing claim and release rules. Leave unanswered release authority and timing after an unresponsive draft check-in explicitly open.
Review sources:
https://github.com/storytold/craft-contrib/pull/4#issuecomment-6207372571https://github.com/storytold/craft-contrib/pull/4#issuecomment-6683543459
This RFC remains a proposal. Add an adoption-time note to align house rule 2 and its copies; do not change the deployed rule now.
Validation: checked the exact original head and numbered rules; UTF-8/LF and trailing newline verified. Documentation only.
* Say what happens when the author of a draft doesn't reply
---------
Co-authored-by: FredApps <153173854+FredApps@users.noreply.github.com>
* Add RFC-0022: A shared GPU layer
* RFC-0022: state the WebGPU optimization headroom explicitly
* RFC-0022: split a joined clause
* RFC-0022: optimization headroom is backend-general, browser particulars noted within it
* RFC-0022: link the draft PR
* RFC-0022: acceptance requirements for the capability model
* Update references after the 0024/0025 renumber
Every Rust Craft app already ships unicode-ident and the ICU4X crates under
Unicode-3.0, but the shared allowlist doesn't name it, and a repository may
not add it to its own copy.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The hosted image pins SoundCraft 0.17.1, not 0.14.0 or 0.15.0. The hard-link
write is soundcraft#1359, with the open fix in soundcraft#1360. EffectCraft
0.21.1 is in the hosted image. Jeremy's end date is recorded, and it is not
counted as the RFC-0000 start.
Co-authored-by: Adithya Shankaran <adikshan11@users.noreply.github.com>
The markers around the copy add 189 bytes, so the file itself has to stay under that. The time rule now links to standards/time.md on craft-contrib, which still resolves after the block is copied into another repository.
Co-authored-by: Cursor <cursoragent@cursor.com>
main is pull requests only. craftrules is retired. plan/ is not a rule source. A pull request does not say an agent wrote it.
Co-authored-by: Cursor <cursoragent@cursor.com>
The comment period closed with the design answers: the joiner owns the status line, fragment ids are issue plus branch slug, the joiner is a craft-libs crate joined nightly, and the craftrules progress-docs standard is confirmed before rollout.
Co-authored-by: Cursor <cursoragent@cursor.com>
TextureCraft ships the flags and MaterialCraft has the lock under other names. Hard-link and
read/write separation rows have now run; one problem turned up, in SoundCraft.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A differently-cased spelling of an in-root file is allowed, so the shared tests cannot treat that row as a refusal.
Co-authored-by: Cursor <cursoragent@cursor.com>
FredApps asked for an RFC-0000 end date and for the Sonar wrapper not to
count as security validation. Neither is in the text yet, and no end-date
comment is recorded. effectcraft#2719 has merged and is not in the 0.19.0
release. soundcraft#1225 is still open, and the hosted image blocks
setup.disk_allocation.
One meaning for --automation-read-root/--automation-write-root across the
Craft CLIs, a shared confine crate in craft-libs, and shared escape tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Calls storytold/craft-common-actions/.github/workflows/sonarcloud.yml@main
with secrets: inherit. Adds SonarCloud badge to README where missing and
removes the redundant sonar-project.properties (config now passed by the
reusable workflow).