Extending Quinzee with a New Capability
A contributor wants to implement additional behaviour for an existing service.
Advanced · Contributor · Source access required
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. Start with the linked book exercises, which document the existing building blocks.
What Quinzee contributes
The module and test descriptions provide an entry point for a controlled source modification.
The proposed example
Choose one missing operation in an existing service, locate its module and capability contract, then design a regression test and implementation change.
Required capabilities
Authorized source access, the native C++ toolchain and regression/compatibility tests.
Boundaries and remaining work
The codebase is proprietary. Publishing internals does not itself grant source access or modification/distribution rights; no stable third-party plugin ABI is promised.
What to verify
- Demonstrate the missing behavior with a focused test.
- Check existing clients, error contracts, persistence and authorization before expanding the advertised support surface.
Read the three perspectives
- The Book of Quinzee: Meet Quinzee and its services
- The Book of Quinzee: Service compatibility and limits
- Quinzee Administrator’s Guide: Understand modules and their dependencies
- Quinzee Internals: Architecture and trust boundaries · Primary reference
- Quinzee Internals: Source layout and conventions · Primary reference
- Quinzee Internals: HTTP library and asynchronous execution · Primary reference
- Quinzee Internals: Connection and streaming lifecycle · Primary reference
- Quinzee Internals: Testing and verification · Primary reference
- Quinzee Internals: Module host and service state · Primary reference