What we accept
- doc improvements
- examples and tutorials
- website fixes
- tooling improvements
.dtsexample review and lab shaping- technical writing feedback
- academic review of database, CS, and education claims
- proof labels for runtime evidence, source evidence, and planned lanes
Academic and education input
x64base is preparing to open more intentionally to academic interest. Useful review includes:
- CS review of algorithms, data structures, command language design, runtime boundaries, and systems-programming lessons.
- database review of DBF lineage, relational modeling, indexing, locking, triggers, table buffering, and mutation safety.
- technical writing review of comments, command contracts, manual sections, terminology, and student-facing explanations.
- general education review of prerequisites, lesson sequencing, accessibility, assessment, and the Laboratory Campus shape.
- learning-theory review across different schools of learning so labs can support reading, repetition, diagrams, command practice, and project-based learning.
Safe first tasks
- Improve one documentation page without changing product claims.
- Convert one
.dtsscript into a lesson outline with prerequisites and expected output. - Suggest or review one Laboratory Campus lesson using the Suggest a Lesson template.
- Add proof labels to one existing command or feature description.
- Review one page for local-path assumptions versus portable public instructions.
- Propose one diagram that clarifies a source-evidenced or runtime-evidenced lane.
PR checklist
- clear title
- minimal diff
- links to relevant docs pages
- screenshots for UI changes (if applicable)
- proof status for feature claims
- mutation warning for examples that change data
- note whether the change is runtime-evidenced, source-evidenced, planned, or review-needed