Orkastery for companies and teams
Each builder in their own network. The company in one.
Ork Mesh brings the builders’ networks into one company network. Enforcement in Git requires the factory receipt before the merge, and telemetry carries each thread’s conduction to any OpenTelemetry destination. Builders keep the IDE or terminal they prefer.
Three questions every decision maker asks.
Anyone accountable for a team that builds with agents needs three answers. None of them takes the tool away from the dev: what changes is that the work goes through the factory, and the factory is accountable.
-
Who is doing what?
Ork Mesh gathers each builder’s roadmaps, reservations and threads in progress in the company network. Whoever reaches an item that is already reserved sees who reserved it, the project and the phase, and only continues as a collaborator or with an agreement. Before the merge, the conflict warning suggests an order.
RM-089 · F1in 0.6.9 RM-089 · F2in 0.6.9 RM-089 · F3in 0.6.10Ork Mesh -
Did what was merged go through the factory?
Enforcement in Git requires the factory receipt tied to the PR commit. In
exigir, no receipt means no merge, wherever the change came from. The basic receipt detects divergence but does not prove authorship; proof comes with the signed receipt, which is planned.RM-089 · F4in 0.6.9 RM-089 · F5in 0.6.10Enforcement in Git -
How do the builders work?
Telemetry carries each phase, decision and prompt to any OpenTelemetry destination. The Grafana dashboards and the indicators by builder and by team are part of telemetry.
RM-090 · F1in 0.6.9 RM-090 · F2in 0.6.9 RM-090 · F4in 0.6.9 RM-090 · F5in 0.6.10Telemetry
Ork Mesh brings the builders’ networks into one company network.
Each builder already has their own Orkastery Network: their machines, worktrees and threads, with a secret-free snapshot in a private repository of theirs. Ork Building Mesh joins these networks into a company Orkastery Network, a private repository on the company’s forge, to which each builder publishes the roadmaps, reservations and threads in progress of each project.
Choose a builder below, or tap a node in the network, to see what they publish to the company network.
Choose a builder
Builder A
- Threads in progress
- 3
- Projects
- web-app, orders-api
- Published reservation
- ORD-31 in the orders-api project
- Main thread phase
- GO
Builder B
- Threads in progress
- 2
- Projects
- orders-api
- Published reservation
- ORD-44 in the orders-api project
- Main thread phase
- CHECK
Builder C
- Threads in progress
- 1
- Projects
- mobile
- Published reservation
- MOB-12 in the mobile project
- Main thread phase
- PLAN
Builder D
- Threads in progress
- 4
- Projects
- data, web-app
- Published reservation
- DAT-20 in the data project
- Main thread phase
- GO
Builder E
- Threads in progress
- 2
- Projects
- orders-api, web-app
- Published reservation
- ORD-52 in the orders-api project
- Main thread phase
- GO
Builder F
- Threads in progress
- 3
- Projects
- infra, data
- Published reservation
- INF-07 in the infra project
- Main thread phase
- SHIP
Goes to the company network
- Roadmap items, state and reservations, per project
- Threads in progress, with phase and item
- The source of each piece of data and the declared gaps
Stays on the builder’s machine
- Worktrees, local paths and the machine name
- Forge and runtime credentials
- Secrets and private data
Comes back from the company network
- The company policy, in
politica.jsonRM-089 · F1in 0.6.9 - Reservations sent back and collaboratorsRM-089 · F2in 0.6.9
- Conflicts between threads of different buildersRM-089 · F3in 0.6.10
- Builder publication RM-089 · F1in 0.6.9
- Policy coming back RM-089 · F1in 0.6.9
- Personal network: machines and worktrees
- Not yet coming back through the network: reservations and collaborators RM-089 · F2in 0.6.9 conflicts RM-089 · F3in 0.6.10
Join the company network in five steps.
The company creates the network and enrolls the builder; the builder accepts with their own account. Nobody enrolls on someone else’s behalf, and credentials never leave the machine.
- Company
The company creates the network
A dedicated private repository on the company’s forge, on GitHub or GitLab.
ork network empresa criar - Company
The company enrolls the builder
By the stable identity of the forge account, which does not change when the login changes.
ork network empresa inscrever - Builder
The builder accepts
With their own authenticated account. Nobody enrolls on someone else’s behalf.
ork network empresa aceitar - Builder
The builder publishes
Each one to their own path, with concurrency-safe writes. No change, no new commit.
ork network empresa publicar - Builder or company
Leaving or revocation
The builder leaves, or the company revokes the enrollment, and sending stops. The credentials never left the machine.
ork network empresa sairork network empresa revogar
Enforcement lives in Git, not in the terminal.
Enforcement in the terminal can be bypassed: the dev calls the runtime directly. Enforcement lives on the forge: the ork-verify check, required across the organization, demands the factory receipt tied to the PR commit, whether the change came from the IDE, Claude Code or Codex. The company raises the level at its own pace. The basic receipt detects divergence but does not prove authorship; proof comes with the signed receipt, which is planned.
- Branch
feature/paymentsmade in the IDE, no thread - Required check
ork ci runlooks for the receipt tied to HEAD - Receiptmissingno factory receipt
- Branch
ork/paymentsthread with a green verify - Required check
ork ci runruns the claims and commands again - Receiptpresentthe receipt HEAD is an ancestor of the PR
- Branch
ork/paymentsnew commit after verify - Required check
ork ci runcompares the receipt with HEAD - ReceiptSHA mismatchchanged outside
.ork-ci/
Check result: Passes and is recorded
The check result records the missing receipt in the policy block. Nothing blocks.
Check result: Passes
The receipt matches the commit, and the claims run again in CI.
Check result: Passes and is recorded
The check result records sha-divergente.
Check result: Passes with a warning
CI shows what is missing: conduct the change in a factory thread. The merge is still possible.
Check result: Passes
The receipt matches the commit, and the claims run again in CI.
Check result: Passes with a warning
CI asks to run verify and ork ci prepare again.
Check result: Fails: ci.recibo.ausente
The required check fails, and the organization rule blocks the merge. The way out is to conduct the change in a factory thread.
Check result: Passes
The receipt matches the commit, the claims run again and the merge is cleared.
Check result: Fails: ci.recibo.sha-divergente
The code changed after verify. Running verify and ork ci prepare again clears the merge.
Enforcement, slice by slice
- Basic receipt on any branchRM-089 · F5in 0.6.10
ork adotar, terminal warning and auditable exceptionRM-089 · F6in development- Strong receipt, signed by the company factoryRM-089 · F7planned
Before starting, the network warns.
When a builder opens a thread on an item another builder has already reserved, the network says who is doing it, in which project and in which phase, and requires the reservation. The second builder only goes ahead as a collaborator or with the agreement of whoever reserved it, attested by the forge.
-
Reservation
Each roadmap item has an owner while someone works on it, and every builder sees the reservation through the company network.
-
Collaborator
Whoever arrives second joins the thread of whoever reserved the item, as a collaborator, instead of opening parallel work.
-
Agreement attested by the forge
Or goes ahead with the agreement of whoever reserved the item, attested by the forge, not by a local statement.
In exigir, an unavailable network blocks opening the thread: an infrastructure failure must not turn into duplicate work.
After the warning
- Early conflict detection across builders and suggested merge orderRM-089 · F3in 0.6.10
From the ledger to the dashboard, with no secret along the way.
Everything the factory does is already in each thread’s ledger. Telemetry turns it into logs in the OpenTelemetry standard, which any collector and Grafana understand. Builders turn it on with ork telemetria ligar, in their machine’s private configuration, and check beforehand, with ork telemetria enviar --dry-run, everything that would leave. Activation by the company policy, at enrollment, comes later, and the builder will be notified.
- on the machine
Thread ledger
Threads, phases, decisions, HITL points, verify, CHECK, commits, merges and prompts.
RM-090 · F1in 0.6.9 RM-090 · F2in 0.6.9 - on the machine
ork telemetria- maps each event to an OpenTelemetry log record
- removes secrets, then private data
- marks a missing prompt as a gap
- identifies the builder as
user.hash, never by name
RM-090 · F1in 0.6.9 RM-090 · F2in 0.6.9 - at the company
OpenTelemetry Collector
Reference model, with no fixed endpoint or credential.
memory_limiterfilter/requiredtransform/sanitizebatch
RM-090 · F4in 0.6.9 - at the company
Loki or another OTLP destination
Two reference configurations that only swap the exporter. No backend is mandatory.
RM-090 · F4in 0.6.9 - at the company
Grafana and SDLC Analytics
- conduction by thread and phase
- prompts and removals
- export health
- maturity by builder and by team
RM-090 · F4in 0.6.9 RM-090 · F5in 0.6.10
Claude Code and Codex already export OpenTelemetry. Correlation links the native session (session.id and conversation.id) to the thread and the phase, without copying the native event. The runtimes’ native content stays off: the full text only travels through the Orkastery path, after removal.
What has shipped and what comes next
- Conduction logs from the ledger in OTLPRM-090 · F1in 0.6.9
- Prompts with local removal of secrets and private dataRM-090 · F2in 0.6.9
- Correlation with Claude Code and CodexRM-090 · F3in 0.6.9
- Reference Collector and Grafana dashboardsRM-090 · F4in 0.6.9
What leaves the machine
- Conduction data for each thread and phase
- The full text of prompts, after local removal of secrets and private data
- The version of the removal policy, for auditing
- Gaps marked when a prompt went missing or failed the check
What never leaves
- Secrets, tokens and authentication headers
- Private terms from the company’s local list
- Home directory, machine name and email
- Any content the removal cannot decide on safely: the event is refused
Maturity without a single score
DORA for delivery, plus the indicators of the agent process, always separate, with no composite score and no target. Each indicator shows the formula, who is counted, the source and the gaps.
-
Merges with a receipt
Merges with a valid receipt relative to the merges the policy covers.
Source: check, receipt and merge
-
Truth held on the first attempt
Threads whose first green verify held until the merge.
Source: verify, receipt HEAD and merge
-
Rework flagged by CHECK
Findings and fix cycles per thread, shown without a target.
Source: CHECK report and phases
-
Decisions, questions and reversals
Separate counts of decisions taken, questions to a human and decisions reversed.
Source: ledger decisions and HITL points
-
Exceptions
Occurrences grouped by reason and by policy.
Source: ledger, receipt and forge
-
Mode usage
Distribution of threads and merges across #Classic, #Maestro, #Auto and #Fast.
Source: thread state and receipt
DORA
Deployment frequency, lead time, change failure rate and time to restore only appear when the company sends deploy and incident events. The ledger alone does not prove a deploy or a production failure; without those events, the dashboard shows “not confirmed”, never an estimate.
Adopt it without stopping the team.
The policy goes up one level at a time, and the team sees the effect before the next one. Each repository picks the level in orkastery.yaml (ci.politica_recibo), and the organization rule on the forge makes the ork-verify check required.
-
observarPilot
One team conducts through the factory. The check records on every PR whether there is a receipt, blocking nothing.
-
avisarWarning
CI shows on every PR what is missing. Devs learn the path without losing a merge.
-
exigirRequirement
Without a valid receipt, the check fails and the organization rule blocks the merge.
What the company needs
- GitHub or GitLab, with the
ork-verifycheck required across the organization - A private repository on the forge for the company network
- An OpenTelemetry Collector, or another OTLP destination, for telemetry
- The CLI 0.6.9 or newer on each machine:
npm install -g @orkastery/cli
Short answers for decision makers.
- Do devs lose their own tools?
- No. The IDE and the terminal stay. What changes is that the work goes through the factory before the merge.
- Where does the data live?
- In the company’s private repository on the forge and in the collector it chooses. Credentials stay on each builder’s machine.
- What about LGPD and other data protection laws?
- The legal assessment belongs to the company. The product declares what leaves the machine, removes secrets and private data before sending, and the builder sees everything that leaves.
- Are we locked into a vendor?
- No. Telemetry goes out in OTLP, an open standard, to any backend. Grafana is the reference, not a requirement.
Bring Ork Mesh to your team.
Tell us how your team works today. The conversation starts at Orkastery’s institutional email.