Forge app
The Forge's own front: announced doors only, with the app's own sign-in on every path.
appRunning the shop6 operationsid forgeapp
How it sits
An app is already assembled from parts, with a face of its own. The counts and the links below are from the platform's spec and the other services' own descriptions.
| Operations | 6 GET 3 · POST 3 |
| Resources | 2 |
| Leaned on by | no other service names it |
| Leans on | none named |
| In recipes | none yet |
What it can do
6 operations in 2 resources, as the spec declares them. Each row is one call; paths are relative to the part.
rulings
| Method | Path | Does |
|---|---|---|
| GET | /api/rulings | Decisions asked of this app's owner — open first. A service caller holds Forge app.rulings.ask; a person must be an answerer (canRule). |
| POST | /api/rulings | Ask the owner a question (question, options 2–6 or none for free text, context, asked_by, issue_url). The answerers are nudged by mesh DM. A service caller hold |
| GET | /api/rulings/{id} | One decision: the question, its options, and the answer when there is one. |
| POST | /api/rulings/{id}/withdraw | Withdraw an open question — the asker (same asked_by), or an in-house person. |
4 operations
recorder
| Method | Path | Does |
|---|---|---|
| POST | /api/recorder | File a recording request (for_email, url, slug, name, purpose). A service caller needs its own X-API-Key to hold Forge app.recorder.request (the kit's service d |
| GET | /api/recorder/pending | The recording requests waiting for the CALLER — a person's cookie, relayed by every Apex app's /api/recorder/pending (apexProxyAsUser). Any signed-in session; i |
2 operations
All the partsRunning the shopThe platform's own id for this service is cbforgeapp.
forge-catalog.json, generated Oct 30, 2026