Deterministic Signing Episodes for Distributed Trust
Thank you for your interest in contributing to the Deterministic Signing Episodes project.
This system is built around strict determinism, auditability, and reproducibility, and all contributions must preserve these guarantees.
Before contributing, please review the core documentation:
- Architecture
- Phase_I
- Phase_II
- Phase_III
- Verification
These documents define the execution model that all contributions must follow.
This project prioritizes:
- deterministic execution
- explicit inputs only
- no randomness
- no hidden or global state
- ephemeral secret handling
- complete auditability
- reproducible tests
Any contribution that introduces nondeterminism will be rejected.
You may contribute in the following areas:
- deterministic episode improvements
- audit record enhancements
- deterministic Shamir reconstruction logic
- zeroization mechanisms
- protocol definitions
- multi‑agent coordination logic
- improving clarity
- adding examples
- refining technical descriptions
- extending Phase II / Phase III guidelines
- deterministic test cases
- reproducibility validation
- audit consistency checks
- threshold reconstruction tests
Relevant docs:
- episode_determinism
- audit_consistency
- shamir_reconstruction
All code must:
- avoid randomness
- avoid system time
- avoid global state
- avoid environment‑dependent behavior
- avoid nondeterministic ordering
- produce identical outputs for identical inputs
All code must:
- use ephemeral secret handling
- zeroize sensitive material
- avoid persistent secrets
- avoid side effects
Relevant docs:
- zeroize
- audit
All new code must include deterministic tests.
Tests must be reproducible across machines and environments.
Create your own fork and clone it locally.
Use a clear, descriptive name:
feature/deterministic-episode-enhancement
fix/audit-record-structure
docs/phase-iii-clarification
Ensure your changes follow:
- deterministic execution rules
- auditability rules
- zeroization rules
- reproducibility rules
Every change must include tests in the tests/ directory.
Your PR must include:
- a clear description
- justification for the change
- confirmation that determinism is preserved
- confirmation that tests pass
All contributions undergo deterministic review:
- execution determinism is validated
- audit record consistency is checked
- zeroization behavior is inspected
- tests must pass reproducibly
- documentation must remain consistent
If a contribution introduces nondeterminism, it will be rejected.
Frozen.
No modifications allowed.
Contributions may extend:
- deterministic SSS
- threshold approval
- multi‑agent coordination
- protocol definitions
Contributions may extend:
- interoperability
- reference integrations
- adoption guidelines
- standardization artifacts
Relevant docs:
- roadmap
Follow Rust best practices:
- explicit types
- no implicit behavior
- clear error handling
- deterministic ordering
- no hidden side effects
By contributing, you agree that your contributions may be incorporated under the project’s licensing model described in:
- legal.md
For questions or coordination, please refer to:
- team.md