Mirror: This repo is a read-only mirror of gitlab.com/vauchi/features. Please open issues and merge requests there.
Gherkin scenarios defining Vauchi behavior. Each scenario should have corresponding tests.
Every scenario is tagged with its implementation status:
@implemented— has passing tests in the test suite@planned— work on it has started and its test is not on main yet; a scenario nobody is working on is not published here@wip— actively being implemented (temporary, feature branches only)
This repository describes what Vauchi does. Scenarios for features that are not being built yet are kept with the maintainers' planning notes and published here when work on them starts.
Use grep -c '@implemented' *.feature to get live implementation counts.
Ideas and brainstorming live in _private/features/ideas/ (not in this repo).
Scenario counts and implementation status are live data — count them, don't read them here (this README once carried a 2026-02 snapshot that drifted 40% off):
grep -rc "Scenario:" features/*.feature # scenarios per file
just grep "@implemented" features # implemented tally- P0 (Core): Required for MVP. Must work before any release.
- P1 (Security): Security-critical features. Required for public launch.
- P2 (Infrastructure): Relay, federation, labels. Enhances reliability.
- P3 (Post-launch): Advanced privacy features. Opt-in, can ship later.
# Run all tests (includes scenario coverage)
cargo test
# Run tests for specific feature area
cargo test identity
cargo test exchange
cargo test sync- Write scenario in appropriate
.featurefile - Write failing test referencing the scenario
- Implement minimal code to pass
- Refactor while green
See TDD Rules for methodology.