HumanLayer organizes collaborative coding-agent work. Decionis governs authority for an exact consequential action.
Public sources checked . Our architectural assessment follows the scope of the sources below. Send a correction; accepted corrections update this date.
| Dimension | Decionis | HumanLayer |
|---|---|---|
| Control boundary | One exact action, with authority re-evaluated immediately before commit. | HumanLayer's current product is a multiplayer coding-agent IDE and cloud, bringing sessions, plans and code diffs into a shared workspace. |
| Evidence | Signed Decision Dossier; verify the covered artifacts with the appropriate public keys, without an account. | Its public repository now describes much of the old code as deprecated and points to the rebuilt product. Older approval-SDK comparisons are not an accurate description of today's offering. |
| Deployment responsibility | The integrating host must isolate credentials, prevent bypass and enforce the decision. | Evaluate the chosen deployment and its enforcement boundary; a product category is not evidence of a specific installation. |
| Procurement posture | SOC 2 in progress. These pages address engineering and architecture, not certification equivalence. | Obtain current assurance documents and check the service and deployment they cover. |
Decionis contract: enforce-and-bind, claim-before-commit and finalize. Signature validity is separate from execution eligibility and downstream effect confirmation.
A coding workspace and an execution authority address different layers. Assess the actual integration boundary instead of treating workspace collaboration as a missing security feature.
Check the evidence
This preloaded dossier has real Ed25519 signatures over synthetic data from the public Agent-Safe corpus. Its test key is deliberately public. It demonstrates verification and tamper detection; it is not customer evidence, a production signature, or permission to execute.
Ready to check locally
npx -y @decionis/verify --file OwnedExecutionBound.json --jwks Jwks.json
After the page or files load, the signature checks need no network. Installing the CLI may require a connection. Valid signatures establish integrity relative to the selected key, not whether the original facts were true.
A capability not described in the cited public material may still exist. This is a technical comparison of documented controls, not a claim of exhaustive vendor testing.