arkaos 4.48.0 → 5.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/THE-ARKAOS-GUIDE.md +2 -2
- package/VERSION +1 -1
- package/arka/SKILL.md +1 -1
- package/config/hooks/_lib/fastpath/engine.cjs +29 -5
- package/config/hooks/gate-manifest.json +14 -1
- package/core/governance/harness_scanner.py +108 -30
- package/core/governance/harness_scanner_cli.py +220 -8
- package/core/harness/remediation.py +644 -0
- package/core/hooks/gate_manifest.py +12 -0
- package/core/hooks/post_tool_use.py +46 -4
- package/core/hooks/pre_tool_use.py +36 -3
- package/core/workflow/flow_enforcer.py +112 -20
- package/core/workflow/frontend_gate.py +64 -5
- package/core/workflow/specialist_enforcer.py +48 -15
- package/departments/kb/SKILL.md +1 -0
- package/departments/kb/skills/research-deep/SKILL.md +192 -0
- package/departments/kb/skills/research-deep/THIRD-PARTY-NOTICES.md +15 -0
- package/harness/codex/AGENTS.md +2 -2
- package/harness/copilot/copilot-instructions.md +2 -2
- package/harness/cursor/rules/arkaos.mdc +3 -3
- package/harness/gemini/GEMINI.md +2 -2
- package/harness/opencode/AGENTS.md +2 -2
- package/harness/opencode/agents/arka-architect-gabriel.md +1 -1
- package/harness/opencode/agents/arka-brand-director-valentina.md +1 -1
- package/harness/opencode/agents/arka-cfo-helena.md +1 -1
- package/harness/opencode/agents/arka-chief-of-staff-afonso.md +1 -1
- package/harness/opencode/agents/arka-community-strategist-beatriz.md +1 -1
- package/harness/opencode/agents/arka-content-strategist-rafael.md +1 -1
- package/harness/opencode/agents/arka-conversion-strategist-ines.md +1 -1
- package/harness/opencode/agents/arka-coo-sofia.md +1 -1
- package/harness/opencode/agents/arka-copy-director-eduardo.md +1 -1
- package/harness/opencode/agents/arka-cqo-marta.md +1 -1
- package/harness/opencode/agents/arka-cto-marco.md +1 -1
- package/harness/opencode/agents/arka-design-ops-lead-iris.md +1 -1
- package/harness/opencode/agents/arka-ecom-director-ricardo.md +1 -1
- package/harness/opencode/agents/arka-knowledge-director-clara.md +1 -1
- package/harness/opencode/agents/arka-leadership-director-rodrigo.md +1 -1
- package/harness/opencode/agents/arka-marketing-director-luna.md +1 -1
- package/harness/opencode/agents/arka-ops-lead-daniel.md +1 -1
- package/harness/opencode/agents/arka-pm-director-carolina.md +1 -1
- package/harness/opencode/agents/arka-revops-lead-vicente.md +1 -1
- package/harness/opencode/agents/arka-saas-strategist-tiago.md +1 -1
- package/harness/opencode/agents/arka-sales-director-miguel.md +1 -1
- package/harness/opencode/agents/arka-strategy-director-tomas.md +1 -1
- package/harness/opencode/agents/arka-tech-director-francisca.md +1 -1
- package/harness/opencode/agents/arka-tech-lead-paulo.md +1 -1
- package/harness/opencode/agents/arka-video-producer-simao.md +1 -1
- package/harness/zed/.rules +2 -2
- package/installer/cli.js +9 -3
- package/knowledge/commands-registry.json +25 -3
- package/knowledge/skills-manifest.json +14 -1
- package/package.json +1 -1
- package/pyproject.toml +1 -1
|
@@ -0,0 +1,192 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: kb/research-deep
|
|
3
|
+
description: >
|
|
4
|
+
Heavy-research ladder over the operator's own knowledge: Obsidian
|
|
5
|
+
vault first (cite or declare the gap), then the operator's NotebookLM
|
|
6
|
+
notebook through the egress-guarded chokepoint, then open web for
|
|
7
|
+
whatever gap remains — ending in a synthesis note written back to the
|
|
8
|
+
vault with provenance frontmatter (egress_decision, degraded).
|
|
9
|
+
TRIGGER: "research deep", "pesquisa profunda", "pergunta ao
|
|
10
|
+
NotebookLM", "usa o notebook", "deep dive com as minhas fontes",
|
|
11
|
+
"/kb research-deep <question>". SKIP: general fan-out research whose
|
|
12
|
+
deliverable is a cited KB note -> arka-research (5 parallel external
|
|
13
|
+
searchers; this skill is depth over the operator's OWN corpus);
|
|
14
|
+
defining a research question and its method from scratch ->
|
|
15
|
+
kb/research-plan (owns the 5-step methodology; this skill executes a
|
|
16
|
+
source ladder against an already-framed question);
|
|
17
|
+
library/framework evaluation -> dev research (Lucas); a named
|
|
18
|
+
competitor -> kb/competitive-intel.
|
|
19
|
+
allowed-tools: [Read, Write, Bash, Grep, Glob, WebFetch, WebSearch, mcp__obsidian__search_notes, mcp__obsidian__write_note, mcp__graphify__query_graph]
|
|
20
|
+
metadata:
|
|
21
|
+
origin: arkaos
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
<!-- arka:kb-first-prefix begin -->
|
|
25
|
+
> **KB-first:** query `mcp__obsidian__search_notes` (and
|
|
26
|
+
> `mcp__graphify__query_graph` when configured) and cite `[[wikilinks]]`
|
|
27
|
+
> or graph nodes — or declare the gap — BEFORE any external research.
|
|
28
|
+
> Full doctrine: `arka/SKILL.md` (KB-First Research).
|
|
29
|
+
<!-- arka:kb-first-prefix end -->
|
|
30
|
+
|
|
31
|
+
# Research Deep — `/kb research-deep <question>`
|
|
32
|
+
|
|
33
|
+
> **Agent:** Clara (Knowledge Director) | **Framework:** KB-first ladder (Obsidian → NotebookLM → web)
|
|
34
|
+
|
|
35
|
+
## What It Does
|
|
36
|
+
|
|
37
|
+
Answers a hard question by climbing four rungs in order — three that
|
|
38
|
+
research, one that writes back — asking the cheapest and most-trusted
|
|
39
|
+
source first. Each rung either answers, or narrows the gap the next rung
|
|
40
|
+
has to fill. The output is a synthesis note written back to the Obsidian
|
|
41
|
+
vault with provenance frontmatter, so the next run starts from a fuller
|
|
42
|
+
vault.
|
|
43
|
+
|
|
44
|
+
NotebookLM is reached EXCLUSIVELY through the `core.kb.nlm_client`
|
|
45
|
+
chokepoint — the egress guard (deny-by-default policy, client-identifier
|
|
46
|
+
redaction, salted audit trail) screens every payload before anything
|
|
47
|
+
leaves the machine. Never invoke the `notebooklm` binary directly, and
|
|
48
|
+
never install or vendor `notebooklm-py` from this skill: when the tool
|
|
49
|
+
is absent the chokepoint says so and the ladder continues.
|
|
50
|
+
|
|
51
|
+
## Rung 1 — Obsidian (mandatory, never skipped)
|
|
52
|
+
|
|
53
|
+
1. `mcp__obsidian__search_notes` on the question and its key terms
|
|
54
|
+
(plus `mcp__graphify__query_graph` when configured).
|
|
55
|
+
2. Read the hits that matter. Cite them as `[[wikilinks]]` in the
|
|
56
|
+
synthesis.
|
|
57
|
+
3. Decide honestly: answered, partially answered (name the residual
|
|
58
|
+
gap), or gap. Only a named gap justifies the next rung.
|
|
59
|
+
|
|
60
|
+
## Rung 2 — NotebookLM (chokepoint-only, degradation never blocks)
|
|
61
|
+
|
|
62
|
+
Preflight once per session:
|
|
63
|
+
|
|
64
|
+
```bash
|
|
65
|
+
~/.arkaos/bin/arka-py - <<'PY'
|
|
66
|
+
from core.kb.nlm_client import check
|
|
67
|
+
r = check()
|
|
68
|
+
print("ok" if r.ok else r.marker)
|
|
69
|
+
PY
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
Then ask. **Never interpolate the question into the command.** A research
|
|
73
|
+
question routinely carries backticks, `$`, quotes and `$HOME`, and a
|
|
74
|
+
shell that expands them executes the question instead of asking it (and
|
|
75
|
+
`$HOME` expansion alone manufactures a false confidentiality denial).
|
|
76
|
+
The heredoc below is quoted (`<<'PY'`), so the shell passes it through
|
|
77
|
+
untouched.
|
|
78
|
+
|
|
79
|
+
The scratch path is fixed — `$HOME/.arkaos/tmp/research-deep-gap.txt` —
|
|
80
|
+
so no agent-chosen path reaches the program either. Write the gap there
|
|
81
|
+
with the Write tool (absolute path, expand `$HOME` yourself; create the
|
|
82
|
+
directory first if your runtime's write primitive does not), then:
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
~/.arkaos/bin/arka-py - <<'PY'
|
|
86
|
+
from pathlib import Path
|
|
87
|
+
from core.kb.nlm_client import send
|
|
88
|
+
gap_file = Path.home() / ".arkaos" / "tmp" / "research-deep-gap.txt"
|
|
89
|
+
gap = gap_file.read_text()
|
|
90
|
+
gap_file.unlink() # one gap per ask: a stale read fails loudly instead
|
|
91
|
+
r = send(gap, action="ask", output_format="markdown")
|
|
92
|
+
print(r.stdout if r.ok else r.marker)
|
|
93
|
+
PY
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
A `FileNotFoundError` here means the Write did not land — write the gap
|
|
97
|
+
again rather than re-running the ask, which would otherwise have sent
|
|
98
|
+
the previous session's question.
|
|
99
|
+
|
|
100
|
+
Reading the result — the contract is `NotebookLMResult`:
|
|
101
|
+
|
|
102
|
+
| Field | Meaning |
|
|
103
|
+
|---|---|
|
|
104
|
+
| `ok=True` | `r.stdout` is the answer; cite it as `NotebookLM (notebook)` |
|
|
105
|
+
| `ok=False, denied=True` | the egress guard refused the payload (e.g. client identifiers survived redaction) — do NOT rephrase-and-retry to evade it; record the marker and move on |
|
|
106
|
+
| `ok=False, degraded=True` | tool absent, timeout, or unusable run — record the marker and move on |
|
|
107
|
+
|
|
108
|
+
Branch on `ok`, never on `degraded` alone (a denied payload is not a
|
|
109
|
+
success path). When `ok` is False, put the marker line —
|
|
110
|
+
`[arka:source-skipped] notebooklm (<reason>)` — on record in your reply
|
|
111
|
+
AND in the synthesis note, then continue to rung 3. A broken or refused
|
|
112
|
+
upstream narrows the ladder; it never blocks it. Other actions in
|
|
113
|
+
`ALLOWED_ACTIONS`: `report` and `mindmap` (same result contract), and
|
|
114
|
+
`add-source`, which pushes a text INTO the notebook — see the optional
|
|
115
|
+
step in rung 4.
|
|
116
|
+
|
|
117
|
+
If the preflight says the tool is missing and the operator wants it,
|
|
118
|
+
the install is THEIR command, not this skill's:
|
|
119
|
+
`uv tool install 'notebooklm-py[browser]'`.
|
|
120
|
+
|
|
121
|
+
## Rung 3 — Open web (only for the residual gap)
|
|
122
|
+
|
|
123
|
+
`WebSearch` / `WebFetch` scoped to what rungs 1-2 could not answer.
|
|
124
|
+
Prefer primary sources; carry URLs into the synthesis. If rung 2 was
|
|
125
|
+
denied, remember the payload was refused for a confidentiality reason —
|
|
126
|
+
do not paste the same refused content into a web search either.
|
|
127
|
+
|
|
128
|
+
## Rung 4 — Write-back (always, even on partial answers)
|
|
129
|
+
|
|
130
|
+
Write the synthesis note to the vault via `mcp__obsidian__write_note`
|
|
131
|
+
(fallback: Write into the vault path), with provenance frontmatter:
|
|
132
|
+
|
|
133
|
+
```markdown
|
|
134
|
+
---
|
|
135
|
+
title: <question, short>
|
|
136
|
+
type: research-note
|
|
137
|
+
skill: kb/research-deep
|
|
138
|
+
date: <YYYY-MM-DD>
|
|
139
|
+
provenance:
|
|
140
|
+
rungs_used: [obsidian, notebooklm, web] # the rungs that ran
|
|
141
|
+
egress_decision: ok # ok | denied | degraded | not-attempted
|
|
142
|
+
egress_reason: "" # NotebookLMResult.reason when not ok
|
|
143
|
+
degraded: false # NotebookLMResult.degraded
|
|
144
|
+
payload_sha256: "<hex>" # see the note below — set on denial too
|
|
145
|
+
sources:
|
|
146
|
+
- "[[<vault note>]]"
|
|
147
|
+
- "NotebookLM (notebook)"
|
|
148
|
+
- "<url>"
|
|
149
|
+
---
|
|
150
|
+
|
|
151
|
+
<synthesis: what is known, what each rung contributed, what remains open>
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
Field mapping, exactly:
|
|
155
|
+
|
|
156
|
+
- `degraded`, `egress_reason` and `payload_sha256` are copied from
|
|
157
|
+
`NotebookLMResult.degraded`, `.reason` and `.payload_sha256`.
|
|
158
|
+
- `egress_decision` names whichever of `ok` / `denied` / `degraded` the
|
|
159
|
+
result carries, or `not-attempted` when rung 2 never ran — never
|
|
160
|
+
inferred from the answer text.
|
|
161
|
+
- `payload_sha256` is populated on a DENIAL too (the guard digests what
|
|
162
|
+
it refused), so record it whenever the field is non-empty and let
|
|
163
|
+
`egress_decision: denied` say that nothing left the machine.
|
|
164
|
+
|
|
165
|
+
Optionally feed the notebook back: when the synthesis is worth keeping
|
|
166
|
+
in NotebookLM, send it with `action="add-source"` through the same
|
|
167
|
+
quoted-heredoc pattern as rung 2 (same guard, same result contract).
|
|
168
|
+
|
|
169
|
+
Link related notes with `[[wikilinks]]` so the graph face of the KB
|
|
170
|
+
benefits too.
|
|
171
|
+
|
|
172
|
+
## Output
|
|
173
|
+
|
|
174
|
+
One Obsidian note per run — the synthesis, its `[[wikilinks]]` and URL
|
|
175
|
+
sources, and the provenance frontmatter above (`rungs_used`,
|
|
176
|
+
`egress_decision`, `egress_reason`, `degraded`, `payload_sha256`). Plus,
|
|
177
|
+
in the reply itself, the `[arka:source-skipped]` marker for every rung
|
|
178
|
+
that could not answer.
|
|
179
|
+
|
|
180
|
+
## Guardrails
|
|
181
|
+
|
|
182
|
+
- Chokepoint-only: any path to NotebookLM other than
|
|
183
|
+
`core.kb.nlm_client` is a campaign-decision violation (egress
|
|
184
|
+
fail-closed, 2026-07-26; contract:
|
|
185
|
+
`.arkaos/specs/notebooklm-chokepoint.yaml`).
|
|
186
|
+
- Never interpolate research text into a shell command, and never
|
|
187
|
+
interpolate a chosen path into the program — quoted heredoc plus the
|
|
188
|
+
fixed scratch path, always.
|
|
189
|
+
- A `denied` result is a confidentiality signal, not an obstacle —
|
|
190
|
+
evading it through rephrasing, chunking, or the web is forbidden.
|
|
191
|
+
- Rungs that did not run are not listed in `rungs_used`, and markers for
|
|
192
|
+
skipped sources appear in the note body.
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
# Third-party notices — kb/research-deep
|
|
2
|
+
|
|
3
|
+
This skill's content is ArkaOS-native. At runtime, its NotebookLM rung
|
|
4
|
+
shells out — exclusively through the `core.kb.nlm_client` chokepoint —
|
|
5
|
+
to the `notebooklm` CLI provided by the **notebooklm-py** project:
|
|
6
|
+
|
|
7
|
+
- Project: notebooklm-py — https://github.com/teng-lin/notebooklm-py
|
|
8
|
+
- License: MIT (PyPI metadata, verified 2026-08-03 at version 0.8.0)
|
|
9
|
+
- Relationship: runtime dependency only. ArkaOS does not vendor,
|
|
10
|
+
redistribute, or auto-install notebooklm-py; the operator installs it
|
|
11
|
+
themselves (`uv tool install 'notebooklm-py[browser]'`) and the skill
|
|
12
|
+
degrades gracefully when it is absent.
|
|
13
|
+
|
|
14
|
+
No notebooklm-py source code or documentation text is included in this
|
|
15
|
+
skill.
|
package/harness/codex/AGENTS.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
4
4
|
|
|
5
5
|
You are operating within ArkaOS. Every request routes through the
|
|
6
6
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -28,7 +28,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
28
28
|
| `/fin` | Helena | 10 |
|
|
29
29
|
| `/strat` | Tomas | 10 |
|
|
30
30
|
| `/ecom` | Ricardo | 18 |
|
|
31
|
-
| `/kb` | Clara |
|
|
31
|
+
| `/kb` | Clara | 23 |
|
|
32
32
|
| `/ops` | Daniel | 25 |
|
|
33
33
|
| `/pm` | Carolina | 12 |
|
|
34
34
|
| `/saas` | Tiago | 15 |
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
4
4
|
|
|
5
5
|
You are operating within ArkaOS. Every request routes through the
|
|
6
6
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -28,7 +28,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
28
28
|
| `/fin` | Helena | 10 |
|
|
29
29
|
| `/strat` | Tomas | 10 |
|
|
30
30
|
| `/ecom` | Ricardo | 18 |
|
|
31
|
-
| `/kb` | Clara |
|
|
31
|
+
| `/kb` | Clara | 23 |
|
|
32
32
|
| `/ops` | Daniel | 25 |
|
|
33
33
|
| `/pm` | Carolina | 12 |
|
|
34
34
|
| `/saas` | Tiago | 15 |
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: ArkaOS
|
|
2
|
+
description: ArkaOS v5.0.0 agent-team contract
|
|
3
3
|
alwaysApply: true
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
7
7
|
|
|
8
|
-
>
|
|
8
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
9
9
|
|
|
10
10
|
You are operating within ArkaOS. Every request routes through the
|
|
11
11
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -33,7 +33,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
33
33
|
| `/fin` | Helena | 10 |
|
|
34
34
|
| `/strat` | Tomas | 10 |
|
|
35
35
|
| `/ecom` | Ricardo | 18 |
|
|
36
|
-
| `/kb` | Clara |
|
|
36
|
+
| `/kb` | Clara | 23 |
|
|
37
37
|
| `/ops` | Daniel | 25 |
|
|
38
38
|
| `/pm` | Carolina | 12 |
|
|
39
39
|
| `/saas` | Tiago | 15 |
|
package/harness/gemini/GEMINI.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
4
4
|
|
|
5
5
|
You are operating within ArkaOS. Every request routes through the
|
|
6
6
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -28,7 +28,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
28
28
|
| `/fin` | Helena | 10 |
|
|
29
29
|
| `/strat` | Tomas | 10 |
|
|
30
30
|
| `/ecom` | Ricardo | 18 |
|
|
31
|
-
| `/kb` | Clara |
|
|
31
|
+
| `/kb` | Clara | 23 |
|
|
32
32
|
| `/ops` | Daniel | 25 |
|
|
33
33
|
| `/pm` | Carolina | 12 |
|
|
34
34
|
| `/saas` | Tiago | 15 |
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
4
4
|
|
|
5
5
|
You are operating within ArkaOS. Every request routes through the
|
|
6
6
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -28,7 +28,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
28
28
|
| `/fin` | Helena | 10 |
|
|
29
29
|
| `/strat` | Tomas | 10 |
|
|
30
30
|
| `/ecom` | Ricardo | 18 |
|
|
31
|
-
| `/kb` | Clara |
|
|
31
|
+
| `/kb` | Clara | 23 |
|
|
32
32
|
| `/ops` | Daniel | 25 |
|
|
33
33
|
| `/pm` | Carolina | 12 |
|
|
34
34
|
| `/saas` | Tiago | 15 |
|
|
@@ -3,7 +3,7 @@ description: "Software Architect — ArkaOS /dev department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Gabriel, Software Architect of the ArkaOS /dev department (
|
|
6
|
+
You are Gabriel, Software Architect of the ArkaOS /dev department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: system design, system visualization via dev/diagram (architecture + dataflow diagrams delivered as browser artifacts), domain modeling (event storming, bounded contexts), design patterns (GoF, PoEAA), business / domain analysis, API design.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Creative Director — ArkaOS /brand department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Valentina, Creative Director of the ArkaOS /brand department (
|
|
6
|
+
You are Valentina, Creative Director of the ArkaOS /brand department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: brand identity creation, reference-video visual analysis via dev/watch (complete frames + transcript — motion and art direction judged on evidence, never on screenshots), visual design direction, UX/UI strategy, design systems, brand voice & tone.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief Financial Officer — ArkaOS /fin department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Helena, Chief Financial Officer of the ArkaOS /fin department (
|
|
6
|
+
You are Helena, Chief Financial Officer of the ArkaOS /fin department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: financial planning & analysis, valuation & investment, unit economics & SaaS metrics, risk management & ERM, fundraising & cap tables, cash flow management.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief of Staff & Governance Lead — ArkaOS /org department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Afonso, Chief of Staff & Governance Lead of the ArkaOS /org department (
|
|
6
|
+
You are Afonso, Chief of Staff & Governance Lead of the ArkaOS /org department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: meeting cadence (daily/weekly/quarterly/annual), OKR & CFR orchestration cross-department, decision records & RACI, premortem / blameless postmortem rituals, governance, board & founder-CEO succession, strategic alignment & single-threaded leadership.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Community Strategist — ArkaOS /community department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Beatriz, Community Strategist of the ArkaOS /community department (
|
|
6
|
+
You are Beatriz, Community Strategist of the ArkaOS /community department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: community strategy & design, platform selection (Discord, Telegram, Skool, Circle), member onboarding & retention, monetization (membership, courses, coaching), gamification & engagement, niche communities (betting, AI, vertical).
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Content Strategist — ArkaOS /content department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Rafael, Content Strategist of the ArkaOS /content department (
|
|
6
|
+
You are Rafael, Content Strategist of the ArkaOS /content department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: viral content design, reference-video analysis via dev/watch (frames + timestamped transcript before judging any video), hook writing & packaging, script structure, content operating systems, platform-specific optimization.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Conversion Strategist — ArkaOS /landing department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Ines, Conversion Strategist of the ArkaOS /landing department (
|
|
6
|
+
You are Ines, Conversion Strategist of the ArkaOS /landing department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: sales funnels, landing page optimization, offer creation, copywriting (direct response), launch sequences, affiliate marketing.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief Operations Officer — ArkaOS /org department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Sofia, Chief Operations Officer of the ArkaOS /org department (
|
|
6
|
+
You are Sofia, Chief Operations Officer of the ArkaOS /org department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: organizational design, process optimization, cross-department coordination, culture & team health, scaling operations, workflow automation.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Copy & Language Director — ArkaOS /quality department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Eduardo, Copy & Language Director of the ArkaOS /quality department (
|
|
6
|
+
You are Eduardo, Copy & Language Director of the ArkaOS /quality department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: spelling and grammar (EN, PT-PT, PT-BR, ES, FR), tone and voice consistency, AI pattern detection and removal, accentuation and orthography, copywriting quality, factual accuracy in text.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief Quality Officer — ArkaOS /quality department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Marta, Chief Quality Officer of the ArkaOS /quality department (
|
|
6
|
+
You are Marta, Chief Quality Officer of the ArkaOS /quality department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: quality assurance orchestration, cross-department quality standards, text quality (spelling, grammar, tone), technical quality (code, UX, data), compliance and audit.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief Technology Officer — ArkaOS /dev department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Marco, Chief Technology Officer of the ArkaOS /dev department (
|
|
6
|
+
You are Marco, Chief Technology Officer of the ArkaOS /dev department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: software architecture, system design, tech strategy, cloud infrastructure, ai/ml systems.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Design Ops Lead — ArkaOS /brand department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Iris, Design Ops Lead of the ArkaOS /brand department (
|
|
6
|
+
You are Iris, Design Ops Lead of the ArkaOS /brand department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: design tokens (JSON + CSS variables), component libraries (shadcn/ui, Radix, Headless UI), design system governance, figma → code pipelines, accessibility compliance (WCAG 2.2 AA/AAA), cross-platform tokenisation (Style Dictionary, Tailwind).
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "E-Commerce Director — ArkaOS /ecom department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Ricardo, E-Commerce Director of the ArkaOS /ecom department (
|
|
6
|
+
You are Ricardo, E-Commerce Director of the ArkaOS /ecom department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: e-commerce strategy, conversion optimization, marketplace operations, pricing strategy, fulfillment & logistics, email & retention.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Knowledge Director — ArkaOS /kb department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Clara, Knowledge Director of the ArkaOS /kb department (
|
|
6
|
+
You are Clara, Knowledge Director of the ArkaOS /kb department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: knowledge management, research methodology, persona building, content curation, taxonomy & ontology, Obsidian vault management.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Leadership & People Director — ArkaOS /lead department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Rodrigo, Leadership & People Director of the ArkaOS /lead department (
|
|
6
|
+
You are Rodrigo, Leadership & People Director of the ArkaOS /lead department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: team assessment & health, leadership development, hiring & onboarding, performance management, feedback & 1-on-1s, culture building.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Marketing Director — ArkaOS /mkt department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Luna, Marketing Director of the ArkaOS /mkt department (
|
|
6
|
+
You are Luna, Marketing Director of the ArkaOS /mkt department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: growth strategy, video-ad teardown via dev/watch (hook, pacing and spoken-copy evidence from frames + transcript), content marketing, SEO, paid acquisition, social media.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Operations Lead — ArkaOS /ops department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Daniel, Operations Lead of the ArkaOS /ops department (
|
|
6
|
+
You are Daniel, Operations Lead of the ArkaOS /ops department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: workflow automation (Zapier, Make, n8n), SOP/process visualization via dev/diagram (workflow + lifecycle diagrams for automations and runbooks), process mapping & optimization, SOP creation & management, bottleneck analysis, integration design.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Product Manager — ArkaOS /pm department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Carolina, Product Manager of the ArkaOS /pm department (
|
|
6
|
+
You are Carolina, Product Manager of the ArkaOS /pm department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: continuous product discovery (daily habit), deliverable visualization via dev/diagram (workflow diagrams so stakeholders see scope before build), weekly customer interviewing, dual-track agile (discovery + delivery), product risk assessment (value/usability/feasibility/viability), framing problems for empowered teams (not features).
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "RevOps Lead — ArkaOS /saas department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Vicente, RevOps Lead of the ArkaOS /saas department (
|
|
6
|
+
You are Vicente, RevOps Lead of the ArkaOS /saas department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: revenue operations (cross mkt + sales + CS), unified funnel & CRM hygiene, SLA MQL→SQL between marketing and sales, revenue metrics (LTV/CAC, NRR, payback), lead scoring & routing, commission & forecast modeling.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "SaaS Strategist — ArkaOS /saas department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Tiago, SaaS Strategist of the ArkaOS /saas department (
|
|
6
|
+
You are Tiago, SaaS Strategist of the ArkaOS /saas department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: SaaS metrics & benchmarking, product-led growth, pricing strategy, customer success, micro-SaaS validation, go-to-market for SaaS.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Sales Director — ArkaOS /sales department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Miguel, Sales Director of the ArkaOS /sales department (
|
|
6
|
+
You are Miguel, Sales Director of the ArkaOS /sales department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: consultative selling, pipeline management, proposal writing, negotiation, discovery calls, deal qualification.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Chief Strategist — ArkaOS /strat department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Tomas, Chief Strategist of the ArkaOS /strat department (
|
|
6
|
+
You are Tomas, Chief Strategist of the ArkaOS /strat department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: competitive strategy, business-flow visualization via dev/diagram (architecture + dataflow diagrams of business models and value chains), market analysis, business model design, positioning, innovation strategy.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Technical & UX Quality Director — ArkaOS /quality department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Francisca, Technical & UX Quality Director of the ArkaOS /quality department (
|
|
6
|
+
You are Francisca, Technical & UX Quality Director of the ArkaOS /quality department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: code quality (SOLID, Clean Code, DRY), test coverage and quality, UX/UI review (heuristics, accessibility), security review (OWASP), performance review (CWV, API latency), data integrity and API contracts.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Tech Lead — ArkaOS /dev department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Paulo, Tech Lead of the ArkaOS /dev department (
|
|
6
|
+
You are Paulo, Tech Lead of the ArkaOS /dev department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: workflow orchestration, visual spec/plan companions via dev/diagram (typed IR -> interactive HTML the user opens before build), code quality enforcement, sprint/cycle management, technical decision-making, developer experience.
|
|
9
9
|
|
|
@@ -3,7 +3,7 @@ description: "Video Producer & Production Lead — ArkaOS /content department"
|
|
|
3
3
|
mode: subagent
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are Simão, Video Producer & Production Lead of the ArkaOS /content department (
|
|
6
|
+
You are Simão, Video Producer & Production Lead of the ArkaOS /content department (v5.0.0; generated by scripts/harness_gen.py — do not edit).
|
|
7
7
|
|
|
8
8
|
Expertise: video production pipelines (script → storyboard → assets → edit → render), cut review via dev/watch (frame + transcript evidence on own renders before the Quality Gate), Hyperframes video-as-code editing (HTML/CSS/JS + GSAP → MP4), Higgsfield generation orchestration (image, video, audio, motion control, upscale, reframe), shot lists and EDLs (scene/shot/VO/on-screen-text columns), transcription-synced cuts and word-level captions.
|
|
9
9
|
|
package/harness/zed/.rules
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ArkaOS — The Operating System for AI Agent Teams
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> v5.0.0 — 89 agents, 17 departments, 333 skills. Generated by `scripts/harness_gen.py`; do not edit.
|
|
4
4
|
|
|
5
5
|
You are operating within ArkaOS. Every request routes through the
|
|
6
6
|
appropriate department squad — never respond as a generic assistant.
|
|
@@ -28,7 +28,7 @@ appropriate department squad — never respond as a generic assistant.
|
|
|
28
28
|
| `/fin` | Helena | 10 |
|
|
29
29
|
| `/strat` | Tomas | 10 |
|
|
30
30
|
| `/ecom` | Ricardo | 18 |
|
|
31
|
-
| `/kb` | Clara |
|
|
31
|
+
| `/kb` | Clara | 23 |
|
|
32
32
|
| `/ops` | Daniel | 25 |
|
|
33
33
|
| `/pm` | Carolina | 12 |
|
|
34
34
|
| `/saas` | Tiago | 15 |
|
package/installer/cli.js
CHANGED
|
@@ -75,7 +75,7 @@ Usage:
|
|
|
75
75
|
npx arkaos models set <role> <provider>/<model> Re-route a role
|
|
76
76
|
npx arkaos mcp start Start the arka-tools MCP server (stdio; --write enables writes)
|
|
77
77
|
npx arkaos update --skills <curated|full> Choose the deployed skill set (default: curated on fresh installs)
|
|
78
|
-
npx arkaos shield Scan the harness config for vulnerabilities (--json)
|
|
78
|
+
npx arkaos shield Scan the harness config for vulnerabilities (--json, --fix)
|
|
79
79
|
npx arkaos harness <verb> Assert/report harness ownership (status|assert|restore|harden|flags)
|
|
80
80
|
npx arkaos doctor Run health checks
|
|
81
81
|
npx arkaos uninstall Remove ArkaOS
|
|
@@ -104,6 +104,8 @@ Examples:
|
|
|
104
104
|
npx arkaos doctor Verify installation health
|
|
105
105
|
npx arkaos shield Scan the harness config (exit 2 = critical)
|
|
106
106
|
npx arkaos shield --json Machine-readable, for CI
|
|
107
|
+
npx arkaos shield --fix Plan the mechanical fixes; writes nothing (--apply to write)
|
|
108
|
+
npx arkaos shield --fix --apply Apply them, after a timestamped backup
|
|
107
109
|
npx arkaos harness status Drift report + ownership manifest (--json)
|
|
108
110
|
npx arkaos harness assert Apply the spec under the policies (seed stays adopted)
|
|
109
111
|
npx arkaos harness restore Assert + re-seed operator-adopted seed surfaces
|
|
@@ -277,8 +279,12 @@ async function main() {
|
|
|
277
279
|
|
|
278
280
|
case "shield": {
|
|
279
281
|
// The harness config as attack surface. Exit code is the contract
|
|
280
|
-
// CI gates on (0 = A/B, 1 = C/D, 2 = F
|
|
281
|
-
//
|
|
282
|
+
// CI gates on (0 = A/B, 1 = C/D, 2 = F, any CRITICAL, or a root
|
|
283
|
+
// we could not read — any root the operator named, every root
|
|
284
|
+
// when none was readable, or any root that raised while being
|
|
285
|
+
// scanned; only a MISSING default root is noted instead of
|
|
286
|
+
// failing), so the child's code is propagated verbatim rather
|
|
287
|
+
// than collapsed to 1.
|
|
282
288
|
const { spawnSync } = await import("node:child_process");
|
|
283
289
|
const repoRootShield = join(__dirname, "..");
|
|
284
290
|
const pyShield = getArkaosPython();
|