Resources / Where humans are involved
Copy page as MarkdownJoin the sandbox waitlist

Where humans are involved

This system automates verification, not judgement. Ten points in the loop involve a person, and each one has an owner, a trigger, and a clock. They are listed here because "no one in the middle" was a claim v0.1 made twice and could not support — and because a human step you did not plan for is indistinguishable from an outage.

Not automation with exceptions — automation around a small number of decisions that should not be automated.

#StepWhoTriggered byTypical clock
1Project reviewArkreen reviewPOST /v1/projects/{id}:submit3 business days
2Offering compliance reviewArkreen compliancePOST /v1/offerings3–5 business days
3Connector reviewArkreen engineeringConnector submission5 business days
4Device certificationArkreen hardwareThree units submittedPer model, not per unit
5Tier upgrade (T2, T3)KYB and complianceTier applicationVaries by jurisdiction
6Audit samplingIndependent auditorassurance:request-upgradePer audit period
7Anomaly adjudicationArkreen operationsScore above threshold, unresolved past SLAWithin the epoch
8Meter-swap reconciliationArkreen operationsPOST /v1/devices/{id}:meter-swap1–2 business days
9Remediation reviewArkreen operationsassurance:submit-remediation3 business days
10Reserve drawdown approvalArkreen settlementDrawdown request with documentationPer request

Plus, on the partner side

Licence verificationA person checks a service partner's licence against the issuing regulator's register before that partner may sign anything.Legal attestationA licensed partner reads the PPA, the lease, the SPV documents, the insurance, and the permits. This is the step that moves asset_readiness, and there is no version of it that a signature chip performs.Settlement attestationA custodian or bank-side party confirms funds actually arrived.
⚠ compliance.review_required is a person, not a retry

When this webhook fires, no amount of backing off will resolve it. Queue the affected object and surface it to an operator. Integrations that treat it as a transient failure retry for 24 hours and then give up on something that was always going to take a day.

⚠ Human steps are where your timeline actually lives

Signed telemetry takes minutes. Reaching investment_ready takes weeks, and most of that is steps 1, 2, 5, and the legal attestation — none of which move faster because your integration is finished. Start them in parallel.

✓ Automatic protection is not one of these steps

Downgrades fire without approval, immediately, and freeze new issuance on their own. A person is involved only in the correction path, and only after the protective action has already taken effect. That ordering is the point: protection first, judgement second.