Developer Guide
InKCre is a multi-repository system organized around a shared info-base. This guide provides the common mental model and routes you to the repository that owns the details.
InKCre is under active development. The contributor path is usable today, while
ecosystem interfaces remain version-sensitive. Check the Host compatibility of an Extension rather than assuming a stable, standalone SDK.
Choose a path
Contribute to InKCre
Start with Architecture to understand the shared vocabulary and topology. Then use Contributing to locate the owner of the product, cross-unit, runtime, client, UI, or website change you want to make.
Exact setup commands, runtime versions, tests, and pull-request requirements stay in the repository that enforces them.
Build on InKCre
The foundational ecosystem path is participation as an authenticated peer of the shared info-base. Native PostgreSQL and PostgREST are transports over the same admitted, versioned database protocol. Extensions and APIs provide additional integration shapes.
Start with Ecosystem Developers to choose an integration path. To collect from a new service, follow Build a Source Extension: develop your own Python package and test it on a matching Core Host without contributing to Core.
This is not a promise of unrestricted database access or a complete API compatibility policy. The Architecture guide explains the wider model and canonical contracts.
Primary repositories
| Repository | Current role | Development entry |
|---|---|---|
InKCre/docs | Shared product and cross-unit documentation Hub; source of this website | Repository README |
InKCre/core-py | Python core runtime, migrations, and database lifecycle authority | Contributing guide |
InKCre/client-web | Web client, browser-extension workspace, and shared client infrastructure | Repository README |
InKCre/ui | Design system, tokens, and shared web UI packages | Repository README |
The InKCre GitHub organization contains prototypes and historical repositories as well. They are not all equivalent contributor entry points.
Canonical foundations
- Product requirements own the shared product purpose, behavior, and vocabulary.
- Cross-unit technical design owns durable topology, authority, and interoperability contracts.
- Each implementation repository owns its runtime mechanics and executable checks.
Continue to Architecture, or route a concrete change through Contributing.