Oryvin
Oryvin is the engineering direction behind the platform, not just the name of a documentation site.
It is a model for combining governed documentation, source control, automation, deployment, artifact handling, and operational evidence into one system that can increasingly support its own lifecycle.
That is the meaning of the phrase:
Oryvin Builds Itself, Almost.
The goal is not full autonomy. The goal is a system in which more of the repetitive and structural work can be executed through stable contracts, with a human engineer still guiding architecture, approval, and correction.
Why Oryvin exists
Modern engineering environments drift because their parts are disconnected:
- source is separated from documentation
- deployment logic is separated from design intent
- artifacts lose traceability back to source
- operational evidence is scattered across tools
- institutional knowledge ends up in people instead of systems
Oryvin addresses that by treating these concerns as one architecture.
Current direction
Oryvin is also being used to update itself.
Documentation is currently authored in EditorInChief (EIC), the first-generation system built as a local Node.js application. That generation is being upgraded into Wild EditorInChief (WEIC), a multi-user platform built on WildFly, Java, and PostgreSQL.
This matters because the platform is not only documenting the target system. It is also using its own methods, scripts, contracts, and runtime evidence to move from generation 1 to generation 2 under human oversight.
Operating idea
The practical Oryvin loop is:
- capture intent in governed documentation
- keep source authoritative in hg
- build and deploy with explicit baselines
- verify runtime identity through
/health - capture artifacts and evidence
- feed results back into documentation and source
That loop is what makes the system increasingly able to support itself.
Major components
| Component | Role |
|---|---|
| WEIC | authoring, API, and future publishing platform |
| Origin | source retrieval and packaging |
| DropBoxMini | artifact distribution |
| Looker | validation and screenshot evidence |
| Orchestrator | execution of patch, build, deploy, and verification workflows |
| Infrastructure | controlled runtime environment |
Design stance
Oryvin does not try to solve every problem with one bloated system.
It favors a set of focused components with narrow responsibilities and explicit contracts:
- WEIC governs knowledge
- hg remains the source of truth
- Origin pulls and packages from source
- DropBoxMini distributes derived artifacts
- Looker captures evidence
- Orchestrator runs controlled execution flows
The value comes from the integration of those focused parts, not from making one tool do everything.
Related documents
The material formerly split between "Vision" and "Oryvin Builds Itself" has been consolidated here so the strategic narrative, current direction, and generation transition live in one canonical document.