The standard · proposals
Change the standard in public
Anyone can propose a change to the standard. A proposal states the problem, the change and its consequences for existing building blocks. The steering group decides in public and publishes its reasons; accepted changes receive a version number.
Process illustratedSteering group to be formed with contributors
sp-0001 · Add numbers, citations and verbatim passages to the fixed flooropen The fixed floor today holds output contracts and execution reliability. A template can publish a result whose numbers or citations were never checked. Standard Explorer §3, Verification: "Draft 0.1 proposes adding numbers, citations and verbatim passages to the floor." sp-0002 · Describe specialists as filesopen Specialists are defined in code, so a new role cannot be proposed without changing the software. Standard Explorer §8: "Specialists as files: Planned." sp-0003 · Adopt a common format for evaluation recordsdraft Evaluation records written in different formats cannot be compared or aggregated. Standard Explorer §5, Evaluation protocol. sp-0006 · Extend the discipline vocabulary beyond the RISE listopen The E2ET theory lab draws on personas from mathematics, physics, the life sciences, law and the humanities. One RISE project declares mathematics. None of these fields is in the RISE disciplinary scope. Registry validation report on e2er.org/data; E2ET persona tiers (src/theory_lab/persona_roster.py). sp-0005 · Declare discipline, method family and design in every descriptionopen Discovery across thousands of building blocks needs facets that sources rarely declare. Today most method and design tags on e2er.org are inferred from names, and the RISE vocabulary has no method or design facet. Registry data model on e2er.org/data; RISE VOCABULARY.md, "How to extend". sp-0004 · Describe skills in the open Agent Skills format with research fieldsaccepted Skills published by different projects describe themselves differently. Standard Explorer §3, Description.