Documentation
Documentation
CORE is the shared platform under the Runink applications. This guide covers what an admin or a
developer needs to operate it. It is written from the code in the org-runink/core repository;
where a feature is planned or not yet wired, the page says so.
The documentation has five sections, one per console category:
Sign in, the console map, the architecture, and every HTTP route.
The core CLI, coding sessions, the agent fleet, reviews, CI workflows, and the cluster pages.
Models and inference, connections, runners, trust and access, data governance, judgements.
CapEx, rule governance, Resolve, playbooks, Ask, audits and lineage.
The Studio, forge.yaml, central verification, and the /forge/ contract.
How each section is organised
- Getting started: a guided first pass over the category’s pages.
- Task and concept pages: how one part works, with the names you will meet in the console and the code.
- Reference: routes, RPCs, commands, triggers and settings, derived from the source.
- Troubleshooting: real error messages, quoted from the code, with their cause and fix.
Quick reference
| I want to… | Go to… |
|---|---|
| sign in and read the Overview | Overview: Getting started |
find a console page or its ?tab= link | Console map |
look up a core command | CLI reference |
| run CORE’s coding agent | Coding sessions |
| know what an agent does and when it runs | Agent fleet |
| add a data connection | Connections |
| enrol a self-hosted runner | Runners |
| upload a CapEx feed | CapEx |
| verify a FORGE project | Central verification |
| fix an error | the Troubleshooting page of the section |
Cross-cutting questions are in the FAQ.