Security & Permissions
How many reviews a Skill passes before it enters the enterprise, what each Agent can see and do, who intercepts high-risk actions, and why the audit trail lives outside the Agent runtime.
Multi-stage Skill review, role-based isolation, synchronous policy blocking, and an audit trail outside the runtime
- Skills pass the LarkScout three-layer gate and deploy only after human authorization; HarnessServer SkillScan can add a pre-deploy scan
- Agents receive different content by Coordinator / Worker role and class; secrets stay out of context, and memory and knowledge interfaces are off by default
- NodalOS evaluates runtime policies with CEL, and OwlAudit evaluates synchronously on hooks — denying, freezing, or routing to human review on a hit
- OwlAudit holds the audit ledger independently; written records are verifiable with gap checks, and human approvals happen in AULO
- 01Upload a Skill package (ZIP / Tar.gz)
- 02Archive safety: zip bombs / Zip-Slip / symlink escape
- 03SKILL.md and directory checks
- 04Process-isolated YARA scan
- 05Human confirmation and authorization
- 06Optional SkillScan, then deploy
The three-layer ingest gate blocks critical / high matches by default; the YARA layer needs the scanner deployed, and prompt-injection rules do not hard-block by default. SkillScan is off by default and, when enabled, statically scans Python before deployment. These are all static checks, not a runtime sandbox.
HarnessServer distributes different Skills, SOPs, and Rules by Coordinator / Worker visibility and by Agent class, skeleton, and purchased products
Managed memory is off by default and queryable only by Agents granted memory_access; the LarkScout knowledge interface is off by default and accepts mTLS connections only
Secrets are managed via File / Env and never enter Agent context
NodalOS evaluates runtime policies dynamically with CEL (Common Expression Language)
As a synchronous evaluator on connected hooks, OwlAudit can deny an action, write a freeze record, or route it to HITL review according to policy
The audit chain and review tickets are held by OwlAudit, not inside the Agent runtime; written records can be recomputed, verified, and checked for gaps
By role
Technology leaders
Static review, role isolation, and runtime policy form separate layers, each with a clear owner
Compliance & risk
The audit chain is independent of the Agent runtime and written records are verifiable; policy changes carry versions, so the policy in force at the time can be traced
Business leaders
High-risk actions pass policy checks and human review first, and there is an audit record to consult afterwards