alexmandClaude
3831b52a2b
- hashing.algorithm names the hash function in every document; a consumer refuses one it does not implement (doc.hash.algorithm) - ML-DSA-65 (FIPS 204) is an implemented signature scheme: pure-Python reference in tools/oracle/mldsa.py checked against NIST ACVP vectors, a receipt signed by the new roster key dana, and signature vectors for key generation and a deterministic signature - roster keys may carry a did:key, which the validator checks against the public key (doc.roster.did), and a witness purpose for parties that cosign log checkpoints - model provenance: a correction's author and an annotation's generator name the model with provider, version and the hashes of its weights, prompt and parameters, and where it ran - the transparency log gains the tlog-tiles static layout (fixtures/records/log/), a project settings.log with origin, witnesses and threshold, and an acceptance rule; the fixture checkpoint is cosigned by a witness - store.sql: roster_keys accepts cose and ml-dsa-65 and gains a did column - spec chapters 01, 08, 11, 18, 20 and 23, the rationale, glossary, fixture, vector and tool guides updated; stress harness covers ML-DSA Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
20. Projects
A project, scienting-project/1, is the unit a team works in.
| Part | Holds |
|---|---|
key, store, name, description |
Its identity. |
members |
People with a role (owner, editor, reader or guest) and the roster keys they sign with. |
documents |
The project's documents, each with the reason it is included, tags, and a reading status per member: unread, reading or read. |
paths |
Reading paths: ordered steps through documents, nodes, claims and layers, for onboarding a student or preparing a reading group. |
layers, datasets, views, drafts |
What the project holds. |
claims |
The claim namespace or bundle it uses, as the lode setting. |
settings |
The digit rule for targeted F3 (8.10), the drift threshold (6.6), the spot-check rate and minimum (8.8), what happens when a right is unknown (refuse, the default, or warn), the stage requirements in use, as the id of their stage file (14), and the project's transparency log: its origin, the roster keys that witness it, and the threshold of witnesses a checkpoint needs (23). |
Projects are small on purpose: everything about them is designed for hundreds of documents, not millions.
Owners sign policies (14.2).
Who may revoke receipts follows the roster instead: a key whose role in the roster is owner (8.7), so a project's owners hold keys with that role.