arkaos 2.17.1 → 2.17.4
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/VERSION +1 -1
- package/arka/SKILL.md +9 -67
- package/arka/skills/comfyui/SKILL.md +50 -12
- package/arka/skills/conclave/SKILL.md +43 -141
- package/arka/skills/conclave/references/advisors.md +36 -0
- package/arka/skills/human-writing/SKILL.md +15 -100
- package/arka/skills/human-writing/references/forbidden-patterns.md +32 -0
- package/config/hooks/post-tool-use.sh +72 -0
- package/config/hooks/session-start.sh +16 -0
- package/config/hooks/user-prompt-submit.ps1 +2 -2
- package/config/hooks/user-prompt-submit.sh +102 -26
- package/core/agents/__pycache__/behavior_enforcer.cpython-313.pyc +0 -0
- package/core/agents/__pycache__/dna_registry.cpython-313.pyc +0 -0
- package/core/agents/adapters/__pycache__/disc_adapter.cpython-313.pyc +0 -0
- package/core/agents/adapters/disc_adapter.py +149 -0
- package/core/agents/behavior_enforcer.py +255 -0
- package/core/agents/dna_registry.py +235 -0
- package/core/forge/__init__.py +36 -0
- package/core/forge/__pycache__/__init__.cpython-313.pyc +0 -0
- package/core/forge/__pycache__/orchestrator.cpython-313.pyc +0 -0
- package/core/forge/__pycache__/runtime_dispatcher.cpython-313.pyc +0 -0
- package/core/forge/orchestrator.py +770 -0
- package/core/forge/runtime_dispatcher.py +465 -0
- package/core/governance/__pycache__/quality_api.cpython-313.pyc +0 -0
- package/core/governance/__pycache__/quality_router.cpython-313.pyc +0 -0
- package/core/governance/__pycache__/review_workflow.cpython-313.pyc +0 -0
- package/core/governance/quality_api.py +280 -0
- package/core/governance/quality_router.py +304 -0
- package/core/governance/review_workflow.py +386 -0
- package/core/memory/__pycache__/compressor.cpython-313.pyc +0 -0
- package/core/memory/__pycache__/rehydrator.cpython-313.pyc +0 -0
- package/core/memory/__pycache__/session_store.cpython-313.pyc +0 -0
- package/core/memory/compressor.py +269 -0
- package/core/memory/rehydrator.py +204 -0
- package/core/memory/session_store.py +256 -0
- package/core/runtime/__pycache__/context_compactor.cpython-313.pyc +0 -0
- package/core/runtime/__pycache__/subagent.cpython-313.pyc +0 -0
- package/core/synapse/__init__.py +10 -3
- package/core/synapse/__pycache__/__init__.cpython-313.pyc +0 -0
- package/core/synapse/__pycache__/engine.cpython-313.pyc +0 -0
- package/core/synapse/__pycache__/kb_cache.cpython-313.pyc +0 -0
- package/core/synapse/__pycache__/layers.cpython-313.pyc +0 -0
- package/core/synapse/engine.py +27 -16
- package/core/synapse/kb_cache.py +382 -0
- package/core/synapse/layers.py +253 -50
- package/core/sync/__pycache__/self_healing.cpython-313.pyc +0 -0
- package/core/workflow/__pycache__/announcer.cpython-313.pyc +0 -0
- package/core/workflow/__pycache__/dashboard.cpython-313.pyc +0 -0
- package/core/workflow/__pycache__/enforcer.cpython-313.pyc +0 -0
- package/core/workflow/__pycache__/rules_registry.cpython-313.pyc +0 -0
- package/core/workflow/__pycache__/state.cpython-313.pyc +0 -0
- package/core/workflow/announcer.py +246 -0
- package/core/workflow/dashboard.py +194 -0
- package/core/workflow/enforcer.py +234 -0
- package/core/workflow/recovery.py +196 -0
- package/core/workflow/rules_registry.py +484 -0
- package/core/workflow/session_summary.py +204 -0
- package/core/workflow/state.py +12 -2
- package/departments/dev/SKILL.md +10 -42
- package/departments/dev/skills/agent-design/SKILL.md +6 -26
- package/departments/dev/skills/ci-cd-pipeline/SKILL.md +6 -29
- package/departments/dev/skills/db-schema/SKILL.md +6 -24
- package/departments/dev/skills/dependency-audit/SKILL.md +1 -3
- package/departments/dev/skills/incident/SKILL.md +6 -24
- package/departments/dev/skills/mcp-builder/SKILL.md +4 -17
- package/departments/dev/skills/observability/SKILL.md +6 -29
- package/departments/dev/skills/performance-profiler/SKILL.md +5 -26
- package/departments/dev/skills/rag-architect/SKILL.md +5 -23
- package/departments/dev/skills/release/SKILL.md +4 -17
- package/departments/dev/skills/spec/SKILL.md +47 -148
- package/departments/landing/skills/landing-gen/SKILL.md +3 -15
- package/departments/marketing/skills/cold-email/SKILL.md +5 -17
- package/departments/marketing/skills/programmatic-seo/SKILL.md +6 -21
- package/departments/strategy/skills/board-advisor/SKILL.md +7 -21
- package/package.json +1 -1
- package/pyproject.toml +1 -1
- package/scripts/synapse-bridge.py +27 -3
package/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
2.17.
|
|
1
|
+
2.17.4
|
package/arka/SKILL.md
CHANGED
|
@@ -47,23 +47,10 @@ Users don't need to memorize commands. Just describe what you need:
|
|
|
47
47
|
|
|
48
48
|
### Routing Logic
|
|
49
49
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
a. Synapse L1 (Department Detection) matches keywords
|
|
55
|
-
b. Synapse L5 (Command Hints) scores against registry
|
|
56
|
-
c. Hook context [dept:], [hint:] tags from Synapse
|
|
57
|
-
|
|
58
|
-
3. Resolution:
|
|
59
|
-
- Single high-confidence match → Announce squad + execute
|
|
60
|
-
- Multiple matches → Show top 3, ask user to pick
|
|
61
|
-
- No match but clear department → Route to /dept do
|
|
62
|
-
- Ambiguous → Ask "Which department?"
|
|
63
|
-
|
|
64
|
-
4. Code-modifying commands → Show preview, ask confirmation
|
|
65
|
-
Non-code commands → Auto-execute with announcement
|
|
66
|
-
```
|
|
50
|
+
1. Explicit `/prefix` → Route directly
|
|
51
|
+
2. Natural language → Synapse L1 (keyword) + L5 (command hints) + hook context tags
|
|
52
|
+
3. Resolution: single match → announce + execute | multiple → top 3 + ask | ambiguous → ask department
|
|
53
|
+
4. Code-modifying → preview + confirm | non-code → auto-execute
|
|
67
54
|
|
|
68
55
|
### Squad Routing (NON-NEGOTIABLE)
|
|
69
56
|
|
|
@@ -72,24 +59,7 @@ as a generic assistant. Even a one-line task goes through the correct squad work
|
|
|
72
59
|
|
|
73
60
|
## Department Routing Table
|
|
74
61
|
|
|
75
|
-
|
|
76
|
-
|--------|-----------|------------|----------|
|
|
77
|
-
| `/dev` | Development | Paulo (Tech Lead) | 16 |
|
|
78
|
-
| `/mkt` | Marketing & Growth | Luna | 12 |
|
|
79
|
-
| `/brand` | Brand & Design | Valentina | 12 |
|
|
80
|
-
| `/fin` | Finance & Investment | Helena (CFO) | 10 |
|
|
81
|
-
| `/strat` | Strategy & Innovation | Tomas | 10 |
|
|
82
|
-
| `/ecom` | E-Commerce | Ricardo | 12 |
|
|
83
|
-
| `/kb` | Knowledge Management | Clara | 12 |
|
|
84
|
-
| `/ops` | Operations & Automation | Daniel | 10 |
|
|
85
|
-
| `/pm` | Project Management | Carolina | 12 |
|
|
86
|
-
| `/saas` | SaaS & Micro-SaaS | Tiago | 14 |
|
|
87
|
-
| `/landing` | Landing Pages & Funnels | Ines | 14 |
|
|
88
|
-
| `/content` | Content & Viralization | Rafael | 14 |
|
|
89
|
-
| `/community` | Communities & Groups | Beatriz | 14 |
|
|
90
|
-
| `/sales` | Sales & Negotiation | Miguel | 10 |
|
|
91
|
-
| `/lead` | Leadership & People | Rodrigo | 10 |
|
|
92
|
-
| `/org` | Organization & Teams | Sofia (COO) | 10 |
|
|
62
|
+
`/dev` Paulo · `/mkt` Luna · `/brand` Valentina · `/fin` Helena · `/strat` Tomas · `/ecom` Ricardo · `/kb` Clara · `/ops` Daniel · `/pm` Carolina · `/saas` Tiago · `/landing` Ines · `/content` Rafael · `/community` Beatriz · `/sales` Miguel · `/lead` Rodrigo · `/org` Sofia (COO)
|
|
93
63
|
|
|
94
64
|
## Quality Gate (Automatic)
|
|
95
65
|
|
|
@@ -110,44 +80,16 @@ Every workflow includes a Quality Gate phase before delivery:
|
|
|
110
80
|
|
|
111
81
|
## Cross-Department Collaboration
|
|
112
82
|
|
|
113
|
-
|
|
114
|
-
borrowed into ad-hoc project squads. Example:
|
|
115
|
-
|
|
116
|
-
```
|
|
117
|
-
/do "launch campaign for new product"
|
|
118
|
-
→ Creates project squad with:
|
|
119
|
-
- Ines (Landing) — offer + funnel
|
|
120
|
-
- Teresa (Landing) — sales copy
|
|
121
|
-
- Luna (Marketing) — paid + social
|
|
122
|
-
- Isabel (Brand) — visual assets
|
|
123
|
-
- Ricardo (E-Commerce) — store setup
|
|
124
|
-
```
|
|
83
|
+
Matrix structure: agents belong to department squads but can be borrowed into ad-hoc project squads. Example: `/do "launch campaign"` → Ines (Landing) + Luna (Marketing) + Isabel (Brand) + Ricardo (E-Commerce).
|
|
125
84
|
|
|
126
85
|
## Session Greeting
|
|
127
86
|
|
|
128
|
-
|
|
129
|
-
1. Read user profile from ~/.arkaos/profile.json
|
|
130
|
-
2. If profile exists: Show branded welcome with name and company
|
|
131
|
-
3. If no profile: Prompt onboarding via /arka setup
|
|
132
|
-
4. If command provided: Skip greeting, process immediately
|
|
87
|
+
No command: read `~/.arkaos/profile.json` → welcome if exists, else `/arka setup`. Command provided → process immediately.
|
|
133
88
|
|
|
134
89
|
## Obsidian Integration
|
|
135
90
|
|
|
136
|
-
All
|
|
137
|
-
- YAML frontmatter on all files
|
|
138
|
-
- Wikilinks for cross-references
|
|
139
|
-
- Department-specific output paths
|
|
140
|
-
- MOC (Map of Content) for organization
|
|
91
|
+
All output: YAML frontmatter · wikilinks · department paths · MOC organization.
|
|
141
92
|
|
|
142
93
|
## Model Selection
|
|
143
94
|
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
- Agent YAMLs at `departments/*/agents/*.yaml` have `model: opus | sonnet | haiku`
|
|
147
|
-
- Quality Gate dispatch (Marta/Eduardo/Francisca) ALWAYS uses `model: opus` — NON-NEGOTIABLE
|
|
148
|
-
- Default to `sonnet` if the agent YAML has no `model` field
|
|
149
|
-
- Mechanical tasks (commit messages, routing, keyword extraction) use `model: haiku`
|
|
150
|
-
|
|
151
|
-
Example Task tool call:
|
|
152
|
-
|
|
153
|
-
Task(description="...", subagent_type="general-purpose", model="sonnet", prompt="...")
|
|
95
|
+
Use `model` parameter from agent YAML (`departments/*/agents/*.yaml`). Quality Gate (Marta/Eduardo/Francisca) ALWAYS `model: opus` — NON-NEGOTIABLE. Default: `sonnet`. Mechanical tasks: `haiku`.
|
|
@@ -22,14 +22,12 @@ Full-spectrum AI media production platform. From ComfyUI node engineering to Hol
|
|
|
22
22
|
| **purz-comfyui-workflows** | Workflow Collection | ComfyUI JSON (7 workflows, 110+ nodes) | `/Users/andreagroferreira/AIProjects/purz-comfyui-workflows` |
|
|
23
23
|
| **lora_tester** | CLI Tool + Gallery | Python 3.8+ (stdlib) + Vanilla HTML/JS | `/Users/andreagroferreira/AIProjects/lora_tester` |
|
|
24
24
|
|
|
25
|
-
## Squads
|
|
25
|
+
## Squads
|
|
26
26
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
| **ComfyUI Core** | Technical engine: workflow JSON, custom nodes, models, VRAM, API automation | Viktor (Pipeline Architect), Kaito (Workflow Engineer), Iris (Node Researcher), Atlas (Model Specialist), Nexus (Automation Engineer), Pixel (QA Tester) |
|
|
30
|
-
| **Cinematographic Production** | Hollywood pipeline: direction, DP, art, VFX, color, edit, sound, motion, production | Roman (Director), Lena (DP), Soren (Screenwriter), Mika (Art Director), Orion (VFX), Celeste (Colorist), Raven (Editor), Echo (Sound Designer), Flux (Motion Graphics), Sterling (Producer) |
|
|
27
|
+
**ComfyUI Core:** Viktor, Kaito, Iris, Atlas, Nexus, Pixel — workflow JSON, custom nodes, models, VRAM, API.
|
|
28
|
+
**Cinematographic Production:** Roman, Lena, Soren, Mika, Orion, Celeste, Raven, Echo, Flux, Sterling — direction, DP, VFX, color, edit, sound, motion.
|
|
31
29
|
|
|
32
|
-
Full role definitions
|
|
30
|
+
Full role definitions: `references/squads.md`.
|
|
33
31
|
|
|
34
32
|
## Commands
|
|
35
33
|
|
|
@@ -70,13 +68,53 @@ Full role definitions, agent types, and competencies: `references/squads.md`.
|
|
|
70
68
|
|
|
71
69
|
## Orchestration Workflow
|
|
72
70
|
|
|
73
|
-
|
|
71
|
+
6-phase flow: context → analysis+squad routing → plan approval → execution (worktree) → Quality Gate → docs. Squad: technical → Core; creative → Cinematographic; full → both (Sterling coords); research → Iris/Atlas. Details: `references/workflows.md`
|
|
74
72
|
|
|
75
|
-
|
|
73
|
+
<!-- arka:feature:forge-integration:start -->
|
|
74
|
+
## Forge Integration
|
|
76
75
|
|
|
77
|
-
|
|
76
|
+
Complex requests (complexity score >= 5) are automatically routed to
|
|
77
|
+
The Forge for multi-agent planning before execution.
|
|
78
78
|
|
|
79
|
-
|
|
79
|
+
- Phase 0.5: Forge analysis (after spec creation, before squad planning)
|
|
80
|
+
- Complexity assessment: automatic via Synapse L8 (ForgeContextLayer)
|
|
81
|
+
- Manual invocation: `/forge` command
|
|
82
|
+
- Handoff: Forge outputs structured plan -> squad executes phases
|
|
83
|
+
<!-- arka:feature:forge-integration:end -->
|
|
80
84
|
|
|
81
|
-
-
|
|
82
|
-
|
|
85
|
+
<!-- arka:feature:quality-gate:start -->
|
|
86
|
+
## Quality Gate
|
|
87
|
+
|
|
88
|
+
Mandatory on every workflow. Nothing ships without approval.
|
|
89
|
+
|
|
90
|
+
- **Marta (CQO):** Orchestrates review, absolute veto power
|
|
91
|
+
- **Eduardo (Copy Director):** Reviews all text output
|
|
92
|
+
- **Francisca (Tech Director):** Reviews all code and technical output
|
|
93
|
+
- Verdict: APPROVED or REJECTED (binary, no partial)
|
|
94
|
+
<!-- arka:feature:quality-gate:end -->
|
|
95
|
+
|
|
96
|
+
<!-- arka:feature:spec-driven-gate:start -->
|
|
97
|
+
## Spec-Driven Development
|
|
98
|
+
|
|
99
|
+
Phase 0 of all workflows. No implementation begins without a validated spec.
|
|
100
|
+
|
|
101
|
+
- Invocation: automatic before any feature/fix work
|
|
102
|
+
- Gate: spec must be approved before planning phase starts
|
|
103
|
+
- Storage: `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
|
|
104
|
+
- Review: user approval required on written spec
|
|
105
|
+
<!-- arka:feature:spec-driven-gate:end -->
|
|
106
|
+
|
|
107
|
+
<!-- arka:feature:workflow-tiers:start -->
|
|
108
|
+
## Workflow Tiers
|
|
109
|
+
|
|
110
|
+
Three workflow tiers based on task complexity:
|
|
111
|
+
|
|
112
|
+
| Tier | Phases | When |
|
|
113
|
+
|------|--------|------|
|
|
114
|
+
| Enterprise | 7-10 phases | Complex features, multi-file changes |
|
|
115
|
+
| Focused | 3-5 phases | Medium tasks, single-domain changes |
|
|
116
|
+
| Specialist | 1-2 phases | Simple tasks, quick fixes |
|
|
117
|
+
|
|
118
|
+
Tier selection is automatic based on complexity assessment.
|
|
119
|
+
Quality Gate phase is mandatory on ALL tiers.
|
|
120
|
+
<!-- arka:feature:workflow-tiers:end -->
|
|
@@ -9,186 +9,88 @@ allowed-tools: [Read, Write, Edit, Bash, Agent, AskUserQuestion]
|
|
|
9
9
|
|
|
10
10
|
# The Conclave — `/arka conclave`
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
> with codified mental models, thinking styles, and decision frameworks.
|
|
12
|
+
Your personal board of AI advisors. Each based on a real person with codified mental models, thinking styles, and decision frameworks.
|
|
14
13
|
|
|
15
14
|
## Commands
|
|
16
15
|
|
|
17
16
|
| Command | Description |
|
|
18
17
|
|---------|-------------|
|
|
19
|
-
| `/arka conclave` | Start profiling (first time) or view
|
|
20
|
-
| `/arka conclave profile` | Re-run
|
|
18
|
+
| `/arka conclave` | Start profiling (first time) or view board |
|
|
19
|
+
| `/arka conclave profile` | Re-run 17-question DNA profiling |
|
|
21
20
|
| `/arka conclave view` | Display your current advisory board |
|
|
22
21
|
| `/arka conclave ask "<question>"` | Ask all 10 advisors a question |
|
|
23
22
|
| `/arka conclave advisor <name>` | Deep dive on one advisor's mental models |
|
|
24
|
-
| `/arka conclave debate "<topic>"` | Watch
|
|
23
|
+
| `/arka conclave debate "<topic>"` | Watch advisors debate a topic |
|
|
25
24
|
| `/arka conclave aligned` | Show only your 5 aligned advisors |
|
|
26
25
|
| `/arka conclave contrarian` | Show only your 5 contrarian advisors |
|
|
27
26
|
|
|
28
27
|
## First Run: DNA Profiling
|
|
29
28
|
|
|
30
|
-
When
|
|
29
|
+
When `/arka conclave` runs first time (no profile):
|
|
31
30
|
|
|
32
|
-
|
|
33
|
-
```
|
|
34
|
-
Welcome to The Conclave — your personal AI advisory board.
|
|
35
|
-
|
|
36
|
-
I'll ask you 17 questions to understand how you think, decide, and lead.
|
|
37
|
-
This takes about 5 minutes. Your answers determine which advisors match
|
|
38
|
-
your thinking style and which ones will challenge your blind spots.
|
|
39
|
-
|
|
40
|
-
Ready? Let's begin.
|
|
41
|
-
```
|
|
42
|
-
|
|
43
|
-
### Step 2: Ask Questions (one at a time)
|
|
44
|
-
|
|
45
|
-
Use AskUserQuestion tool for each question. Present the options clearly.
|
|
46
|
-
Group by framework with brief context:
|
|
47
|
-
|
|
48
|
-
**Questions 1-4: How you ACT (DISC)**
|
|
49
|
-
- These reveal your behavioral style in work situations
|
|
50
|
-
|
|
51
|
-
**Questions 5-8: What DRIVES you (Enneagram)**
|
|
52
|
-
- These reveal your core motivations and fears
|
|
31
|
+
**Step 1: Welcome** — explain 5-min profiling, ask if ready.
|
|
53
32
|
|
|
54
|
-
**
|
|
55
|
-
- These reveal your personality on 5 continuous scales
|
|
33
|
+
**Step 2: Ask 17 Questions** — one at a time via `AskUserQuestion`:
|
|
56
34
|
|
|
57
|
-
|
|
58
|
-
|
|
35
|
+
| # | Framework | Reveals |
|
|
36
|
+
|---|-----------|---------|
|
|
37
|
+
| 1-4 | DISC | How you ACT in work situations |
|
|
38
|
+
| 5-8 | Enneagram | What DRIVES you (core motivations/fears) |
|
|
39
|
+
| 9-13 | Big Five | Your personality on 5 continuous scales |
|
|
40
|
+
| 14-17 | MBTI | How you THINK and process decisions |
|
|
59
41
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
After all 17 answers:
|
|
42
|
+
**Step 3: Score and Build Profile**
|
|
63
43
|
|
|
64
44
|
1. Load `core.conclave.profiler` module
|
|
65
45
|
2. Create `ProfilingSession`, process each answer
|
|
66
|
-
3. Call `build_profile_from_session()`
|
|
67
|
-
4. Call `match_advisors()`
|
|
68
|
-
5. Save
|
|
69
|
-
|
|
70
|
-
### Step 4: Present the Board
|
|
71
|
-
|
|
72
|
-
Display the board using this format:
|
|
73
|
-
|
|
74
|
-
```markdown
|
|
75
|
-
## Your Behavioral DNA
|
|
76
|
-
|
|
77
|
-
| Framework | Result | Meaning |
|
|
78
|
-
|-----------|--------|---------|
|
|
79
|
-
| DISC | D+C (Driver-Analyst) | Direct, data-driven, results-focused |
|
|
80
|
-
| Enneagram | 5w6 (The Investigator) | Seeks competence, fears being incapable |
|
|
81
|
-
| Big Five | O:78 C:85 E:35 A:40 N:25 | Curious, disciplined, introverted, direct, calm |
|
|
82
|
-
| MBTI | INTJ (The Architect) | Strategic vision + efficient execution |
|
|
83
|
-
|
|
84
|
-
## Your Advisory Board
|
|
85
|
-
|
|
86
|
-
### ALIGNED — Think Like You (amplify your strengths)
|
|
87
|
-
|
|
88
|
-
**1. Charlie Munger** — Vice Chairman, Berkshire Hathaway
|
|
89
|
-
Match: 96% | DNA: C+D, 5w6, ISTJ
|
|
90
|
-
Models: Inversion, Latticework, Circle of Competence
|
|
91
|
-
"What's the downside? Am I treating the symptom or the disease?"
|
|
46
|
+
3. Call `build_profile_from_session()` → `UserProfile`
|
|
47
|
+
4. Call `match_advisors()` → assemble the board
|
|
48
|
+
5. Save to `~/.arkaos/conclave-profile.json`
|
|
92
49
|
|
|
93
|
-
**
|
|
94
|
-
Match: 94% | DNA: D+C, 5w6, INTJ
|
|
95
|
-
Models: Principles-Based Decisions, Radical Transparency
|
|
96
|
-
"What is the principle? Is this based on data or opinion?"
|
|
97
|
-
|
|
98
|
-
[... 3 more aligned ...]
|
|
99
|
-
|
|
100
|
-
### CONTRARIAN — Challenge Your Blind Spots
|
|
101
|
-
|
|
102
|
-
**1. Simon Sinek** — Author, Start With Why
|
|
103
|
-
Match: 35% | DNA: I+S, 2w1, ENFJ
|
|
104
|
-
Challenge: You focus on WHAT and HOW. Simon forces you to ask WHY.
|
|
105
|
-
"What's the WHY? Will people follow because they want to?"
|
|
106
|
-
|
|
107
|
-
**2. Brene Brown** — Research Professor
|
|
108
|
-
Match: 38% | DNA: I+S, 4w3, ENFP
|
|
109
|
-
Challenge: You value control and competence. Brene values vulnerability.
|
|
110
|
-
"Am I being brave enough to be vulnerable?"
|
|
111
|
-
|
|
112
|
-
[... 3 more contrarian ...]
|
|
113
|
-
```
|
|
50
|
+
**Step 4: Present the Board** — show user's DNA (DISC, Enneagram, Big Five, MBTI) + 5 aligned + 5 contrarian advisors with match %, mental models, and signature questions.
|
|
114
51
|
|
|
115
52
|
## Ask Command: `/arka conclave ask "<question>"`
|
|
116
53
|
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
- Use the advisor's communication style
|
|
122
|
-
- Apply their mental models to the question
|
|
123
|
-
- Ask their key questions
|
|
124
|
-
- Keep each response to 3-5 sentences
|
|
125
|
-
3. Present aligned responses first, then contrarian
|
|
126
|
-
4. End with a synthesis: "Where they agree, where they disagree, and what you should consider"
|
|
127
|
-
|
|
128
|
-
### Advisor Response Template
|
|
54
|
+
1. Load `~/.arkaos/conclave-profile.json`
|
|
55
|
+
2. For each of 10 advisors, generate response **in character** (3-5 sentences, their mental models, their questions)
|
|
56
|
+
3. Aligned first, then contrarian
|
|
57
|
+
4. End with synthesis: where they agree/disagree + what to consider
|
|
129
58
|
|
|
130
|
-
|
|
59
|
+
**System prompt approach per advisor:**
|
|
131
60
|
|
|
132
61
|
```
|
|
133
|
-
You are {name}, {title}. You think using
|
|
134
|
-
{
|
|
135
|
-
|
|
136
|
-
Your communication style: {communication_style}
|
|
137
|
-
Your decision framework: {decision_framework}
|
|
138
|
-
|
|
139
|
-
When asked a question, respond in 3-5 sentences as {name} would.
|
|
140
|
-
Use your mental models. Ask your key questions. Be specific to THIS situation.
|
|
141
|
-
Do NOT be generic. Channel {name}'s actual thinking.
|
|
62
|
+
You are {name}, {title}. You think using: {mental_models}.
|
|
63
|
+
Your style: {communication_style}. Your framework: {decision_framework}.
|
|
64
|
+
Respond in 3-5 sentences as {name} would. Be specific. Channel their actual thinking.
|
|
142
65
|
```
|
|
143
66
|
|
|
144
67
|
## Advisor Deep Dive: `/arka conclave advisor <name>`
|
|
145
68
|
|
|
146
|
-
|
|
147
|
-
- Behavioral DNA (all 4 frameworks)
|
|
148
|
-
- All mental models with descriptions and key questions
|
|
149
|
-
- Communication style
|
|
150
|
-
- Decision framework
|
|
151
|
-
- Sources (books, talks)
|
|
152
|
-
- Why they were matched (aligned or contrarian, score, dimension comparison)
|
|
69
|
+
Full advisor profile: all 4 DNA frameworks, mental models with key questions, communication style, decision framework, sources, why matched (aligned/contrarian, score, dimension comparison).
|
|
153
70
|
|
|
154
71
|
## Debate: `/arka conclave debate "<topic>"`
|
|
155
72
|
|
|
156
|
-
1. Present
|
|
157
|
-
2. Each
|
|
73
|
+
1. Present topic to all 10 advisors
|
|
74
|
+
2. Each gives 2-3 sentence take
|
|
158
75
|
3. Identify disagreements between aligned and contrarian groups
|
|
159
|
-
4.
|
|
160
|
-
- Opening positions (each advisor)
|
|
161
|
-
- Key disagreements (which advisors clash and why)
|
|
162
|
-
- Synthesis (what the user should take from both sides)
|
|
76
|
+
4. Structured output: opening positions → key disagreements → synthesis
|
|
163
77
|
|
|
164
78
|
## Profile Persistence
|
|
165
79
|
|
|
166
|
-
-
|
|
167
|
-
- Contains: UserProfile (DNA) + ConclaveBoard (matched advisors)
|
|
80
|
+
- Profile: `~/.arkaos/conclave-profile.json`
|
|
168
81
|
- Re-profile: `/arka conclave profile` overwrites existing
|
|
169
|
-
-
|
|
82
|
+
- Auto-loaded on subsequent calls
|
|
170
83
|
|
|
171
84
|
## The 20 Advisors
|
|
172
85
|
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
| 10 | Derek Sivers | S+C, 9w1, INFP | Hell Yeah or No, opposites, simplicity |
|
|
185
|
-
| 11 | Nassim Taleb | D+C, 8w7, INTJ | Antifragility, barbell, skin in the game |
|
|
186
|
-
| 12 | Seth Godin | I+C, 7w6, ENFP | Purple Cow, permission, smallest audience |
|
|
187
|
-
| 13 | Patrick Lencioni | I+S, 2w1, ENFJ | Five Dysfunctions, trust, healthy conflict |
|
|
188
|
-
| 14 | Warren Buffett | S+C, 5w6, ISTJ | Circle of competence, margin of safety, moats |
|
|
189
|
-
| 15 | Reed Hastings | D+I, 7w8, ENTJ | Talent density, freedom, context not control |
|
|
190
|
-
| 16 | Marty Cagan | C+I, 1w2, INTJ | Empowered teams, discovery before delivery |
|
|
191
|
-
| 17 | Alex Hormozi | D+C, 8w7, ENTJ | Value equation, Grand Slam Offer, Core Four |
|
|
192
|
-
| 18 | April Dunford | C+I, 5w6, INTP | Positioning, 5 components, Obviously Awesome |
|
|
193
|
-
| 19 | James Clear | S+C, 1w9, INFJ | Atomic Habits, systems over goals, 1% better |
|
|
194
|
-
| 20 | Tim Ferriss | D+I, 7w8, ENTP | Fear-setting, 80/20, minimum effective dose |
|
|
86
|
+
Full table with DNA, specialty, and challenge dimension per advisor: `references/advisors.md`
|
|
87
|
+
|
|
88
|
+
## Advisor Response Examples
|
|
89
|
+
|
|
90
|
+
**Charlie Munger (aligned):** "What's the downside? Am I treating the symptom or the disease?"
|
|
91
|
+
|
|
92
|
+
**Simon Sinek (contrarian):** "What's the WHY? Will people follow because they want to, or because they have to?"
|
|
93
|
+
|
|
94
|
+
**Ray Dalio (aligned):** "What is the principle here? Is this based on data or opinion?"
|
|
95
|
+
|
|
96
|
+
**Brene Brown (contrarian):** "Am I being brave enough to be vulnerable here?"
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
# The 20 Advisors — arka-conclave
|
|
2
|
+
|
|
3
|
+
## Aligned Advisors (Think Like You)
|
|
4
|
+
|
|
5
|
+
| # | Name | Title | DNA | Specialty |
|
|
6
|
+
|---|------|-------|-----|-----------|
|
|
7
|
+
| 1 | Charlie Munger | Vice Chairman, Berkshire Hathaway | C+D, 5w6, ISTJ | Inversion, mental models, circle of competence |
|
|
8
|
+
| 2 | Ray Dalio | Founder, Bridgewater Associates | D+C, 5w6, INTJ | Principles, radical transparency, systems |
|
|
9
|
+
| 3 | Naval Ravikant | AngelList Founder | C+D, 5w6, INTP | Leverage, specific knowledge, first principles |
|
|
10
|
+
| 4 | Elon Musk | CEO Tesla/SpaceX/X | D+C, 8w7, INTJ | First principles (physics), 10x thinking |
|
|
11
|
+
| 5 | Steve Jobs | Apple Co-founder | D+I, 3w4, ENTJ | Simplicity, taste, A-players |
|
|
12
|
+
|
|
13
|
+
## Contrarian Advisors (Challenge Your Blind Spots)
|
|
14
|
+
|
|
15
|
+
| # | Name | Title | DNA | Challenge |
|
|
16
|
+
|---|------|-------|-----|-----------|
|
|
17
|
+
| 6 | Simon Sinek | Author, Start With Why | I+S, 2w1, ENFJ | Forces WHY before WHAT/HOW |
|
|
18
|
+
| 7 | Brene Brown | Research Professor | I+S, 4w3, ENFP | Vulnerability over control |
|
|
19
|
+
| 8 | Peter Drucker | Management Consultant | C+S, 1w9, INTJ | Effectiveness, MBO, knowledge workers |
|
|
20
|
+
| 9 | Jeff Bezos | Amazon Founder | D+C, 3w2, ENTJ | Day 1 mindset, working backwards |
|
|
21
|
+
| 10 | Derek Sivers | CD Baby Founder | S+C, 9w1, INFP | Hell Yeah or No, simplicity |
|
|
22
|
+
|
|
23
|
+
## Extended Advisors
|
|
24
|
+
|
|
25
|
+
| # | Name | Title | DNA | Specialty |
|
|
26
|
+
|---|------|-------|-----|-----------|
|
|
27
|
+
| 11 | Nassim Taleb | Author, Antifragile | D+C, 8w7, INTJ | Antifragility, barbell, skin in the game |
|
|
28
|
+
| 12 | Seth Godin | Marketing Author | I+C, 7w6, ENFP | Purple Cow, permission, smallest audience |
|
|
29
|
+
| 13 | Patrick Lencioni | Author, Five Dysfunctions | I+S, 2w1, ENFJ | Trust, healthy conflict, team health |
|
|
30
|
+
| 14 | Warren Buffett | Berkshire Hathaway | S+C, 5w6, ISTJ | Circle of competence, moats, margin of safety |
|
|
31
|
+
| 15 | Reed Hastings | Netflix CEO | D+I, 7w8, ENTJ | Talent density, freedom, context not control |
|
|
32
|
+
| 16 | Marty Cagan | Author, Inspired | C+I, 1w2, INTJ | Empowered teams, discovery before delivery |
|
|
33
|
+
| 17 | Alex Hormozi | Acquisition.com Founder | D+C, 8w7, ENTJ | Value equation, Grand Slam Offer, Core Four |
|
|
34
|
+
| 18 | April Dunford | Positioning Expert | C+I, 5w6, INTP | Positioning, 5 components, Obviously Awesome |
|
|
35
|
+
| 19 | James Clear | Author, Atomic Habits | S+C, 1w9, INFJ | Systems over goals, 1% better |
|
|
36
|
+
| 20 | Tim Ferriss | Author, 4-Hour Workweek | D+I, 7w8, ENTP | Fear-setting, 80/20, minimum effective dose |
|
|
@@ -11,133 +11,48 @@ description: >
|
|
|
11
11
|
|
|
12
12
|
# Human Writing Standard — ARKA OS Core Skill
|
|
13
13
|
|
|
14
|
-
All text produced by ARKA OS must read as if written by a skilled human professional.
|
|
14
|
+
All text produced by ARKA OS must read as if written by a skilled human professional. NON-NEGOTIABLE rule — Constitution #8.
|
|
15
15
|
|
|
16
16
|
## Scope
|
|
17
17
|
|
|
18
|
-
|
|
19
|
-
- Obsidian documents (reports, analyses, specs, ADRs)
|
|
20
|
-
- Terminal responses and summaries
|
|
21
|
-
- Social media posts, captions, stories
|
|
22
|
-
- Email drafts and templates
|
|
23
|
-
- Blog articles and landing page copy
|
|
24
|
-
- Code comments and commit messages
|
|
25
|
-
- PR descriptions and documentation
|
|
26
|
-
- Client-facing deliverables
|
|
18
|
+
Applies to every agent, every department, every output: Obsidian docs, terminal responses, social posts, email drafts, blog articles, landing page copy, code comments, PR descriptions, client deliverables.
|
|
27
19
|
|
|
28
20
|
## Rules
|
|
29
21
|
|
|
30
22
|
### 1. No Dashes as Sentence Connectors
|
|
31
23
|
|
|
32
|
-
Never use em-dashes (—), en-dashes (–), or hyphens (-) to join clauses
|
|
24
|
+
Never use em-dashes (—), en-dashes (–), or hyphens (-) to join clauses. Use commas, semicolons, colons, periods, or conjunctions.
|
|
33
25
|
|
|
34
|
-
**Allowed
|
|
35
|
-
- Compound adjectives: "well-known", "open-source", "pre-commit"
|
|
36
|
-
- Technical terms: "CI/CD", "key-value", "x-axis"
|
|
37
|
-
- Numeric ranges: "2024-2025", "pages 10-15"
|
|
38
|
-
|
|
39
|
-
| Bad | Good |
|
|
40
|
-
|-----|------|
|
|
41
|
-
| The system is fast — it handles 10k requests/s | The system is fast. It handles 10k requests per second. |
|
|
42
|
-
| We need three things — speed, reliability, and cost | We need three things: speed, reliability, and cost. |
|
|
43
|
-
| The API failed — the token had expired | The API failed because the token had expired. |
|
|
44
|
-
| Users can choose dark mode — or stay with light | Users can choose dark mode, or stay with light. |
|
|
26
|
+
**Allowed:** Compound adjectives (well-known, open-source), technical terms (CI/CD, key-value), numeric ranges (2024-2025).
|
|
45
27
|
|
|
46
28
|
### 2. Language Tone and Idioms
|
|
47
29
|
|
|
48
|
-
Match the target language's natural register
|
|
49
|
-
|
|
50
|
-
**Portuguese:** Use Portuguese idioms, sentence rhythm, and phrasing. Do not translate English constructs literally.
|
|
51
|
-
|
|
52
|
-
| Bad (translated English) | Good (natural Portuguese) |
|
|
53
|
-
|--------------------------|---------------------------|
|
|
54
|
-
| "Isso é um jogo-mudador" | "Isto muda completamente o panorama" |
|
|
55
|
-
| "No fim do dia" (literal) | "Em última análise" / "Na prática" |
|
|
56
|
-
| "Nós estamos excitados para anunciar" | "Temos o prazer de anunciar" |
|
|
57
|
-
|
|
58
|
-
**English:** Use natural English rhythm. Avoid overly formal or stiff constructions when the context is conversational.
|
|
30
|
+
Match the target language's natural register. Portuguese: use Portuguese idioms, not translated English constructs. English: natural rhythm, avoid overly formal constructions.
|
|
59
31
|
|
|
60
32
|
### 3. Perfect Accentuation and Spelling
|
|
61
33
|
|
|
62
|
-
Zero tolerance for orthographic errors.
|
|
63
|
-
|
|
64
|
-
**Portuguese examples:**
|
|
65
|
-
- ação (not acção or acao)
|
|
66
|
-
- é, está, será (accents on stressed syllables)
|
|
67
|
-
- informação, coração, posição (ção endings)
|
|
68
|
-
- três, através, português (circumflex and acute)
|
|
69
|
-
- começar, preço, serviço (cedilla)
|
|
70
|
-
|
|
71
|
-
**General:** When uncertain about spelling in any language, verify before outputting. An orthographic error in a client deliverable damages credibility.
|
|
34
|
+
Zero tolerance for orthographic errors. Portuguese: ação, é, três, começar. When uncertain, verify before outputting.
|
|
72
35
|
|
|
73
36
|
### 4. Varied Sentence Structure
|
|
74
37
|
|
|
75
|
-
Mix short and long sentences. Avoid starting consecutive sentences with the same word. Use transitions naturally
|
|
76
|
-
|
|
77
|
-
| Bad (repetitive) | Good (varied) |
|
|
78
|
-
|-------------------|---------------|
|
|
79
|
-
| "The API supports pagination. The API also supports filtering. The API returns JSON." | "The API supports pagination and filtering, returning results as JSON." |
|
|
80
|
-
| "We analyzed the data. We found three patterns. We recommend action." | "Our analysis revealed three patterns. Based on these findings, we recommend immediate action." |
|
|
38
|
+
Mix short and long sentences. Avoid starting consecutive sentences with the same word. Use transitions naturally.
|
|
81
39
|
|
|
82
40
|
### 5. Forbidden AI Patterns
|
|
83
41
|
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
**Forbidden phrases:**
|
|
87
|
-
- "Let's dive in" / "Let's explore"
|
|
88
|
-
- "Here's a breakdown" / "Here's what you need to know"
|
|
89
|
-
- "In conclusion" / "To summarize"
|
|
90
|
-
- "It's worth noting" / "It's important to note"
|
|
91
|
-
- "At the end of the day"
|
|
92
|
-
- "Moving forward"
|
|
93
|
-
- "That being said"
|
|
94
|
-
- "Without further ado"
|
|
95
|
-
- "Game-changer"
|
|
96
|
-
- "Take it to the next level"
|
|
97
|
-
- "Unlock the potential"
|
|
98
|
-
- "In today's fast-paced world"
|
|
99
|
-
|
|
100
|
-
**Forbidden words (use alternatives):**
|
|
101
|
-
| Forbidden | Use Instead |
|
|
102
|
-
|-----------|-------------|
|
|
103
|
-
| leverage | use, apply, build on |
|
|
104
|
-
| utilize | use |
|
|
105
|
-
| streamline | simplify, speed up, reduce steps |
|
|
106
|
-
| robust | reliable, solid, thorough |
|
|
107
|
-
| seamless | smooth, effortless, uninterrupted |
|
|
108
|
-
| cutting-edge | modern, current, recent |
|
|
109
|
-
| empower | enable, support, give tools |
|
|
110
|
-
| synergy | collaboration, combined effect |
|
|
111
|
-
| holistic | complete, full, comprehensive |
|
|
112
|
-
| actionable insights | practical recommendations |
|
|
42
|
+
**Forbidden phrases:** "Let's dive in", "Here's a breakdown", "In conclusion", "It's worth noting", "At the end of the day", "Moving forward", "Game-changer", "Unlock the potential", etc.
|
|
113
43
|
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
Prefer specific facts, numbers, and examples over vague qualitative statements.
|
|
44
|
+
**Forbidden words:** leverage → use | utilize → use | streamline → simplify | robust → reliable | seamless → smooth | empower → enable
|
|
117
45
|
|
|
118
|
-
|
|
119
|
-
|-------------|-----------------|
|
|
120
|
-
| "Significantly improved performance" | "Reduced page load from 3.2s to 0.8s" |
|
|
121
|
-
| "Many users reported issues" | "47 users reported login failures in the last 24 hours" |
|
|
122
|
-
| "The solution is highly scalable" | "The solution handles up to 50k concurrent connections on a single instance" |
|
|
46
|
+
Full list with alternatives: `references/forbidden-patterns.md`
|
|
123
47
|
|
|
124
|
-
###
|
|
48
|
+
### 6. Concrete Over Abstract
|
|
125
49
|
|
|
126
|
-
|
|
50
|
+
Specific facts, numbers, examples over vague statements. "Reduced load from 3.2s to 0.8s" beats "significantly improved performance."
|
|
127
51
|
|
|
128
|
-
|
|
129
|
-
|---------------|---------------|
|
|
130
|
-
| "The feature was implemented by the team" | "The team implemented the feature" |
|
|
131
|
-
| "Errors are logged by the system" | "The system logs errors" |
|
|
132
|
-
| "The report will be generated" | "The system generates the report" |
|
|
52
|
+
### 7. Active Voice by Default
|
|
133
53
|
|
|
134
|
-
|
|
54
|
+
Use active voice unless subject is genuinely unknown. "The team implemented the feature" beats "The feature was implemented by the team."
|
|
135
55
|
|
|
136
56
|
## Enforcement
|
|
137
57
|
|
|
138
|
-
|
|
139
|
-
1. **Constitution L0 injection** — `human-writing` appears in every prompt's NON-NEGOTIABLE list
|
|
140
|
-
2. **Self-critique phase** — Agents review their own output against these rules before delivery
|
|
141
|
-
3. **Cross-department application** — Every department SKILL.md inherits this standard
|
|
142
|
-
|
|
143
|
-
Agents who produce text that violates these rules must revise before delivering output.
|
|
58
|
+
Constitution L0 injection · Self-critique phase before delivery · Cross-department application. Agents who violate must revise before delivering.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Forbidden Writing Patterns — arka-human-writing
|
|
2
|
+
|
|
3
|
+
## Forbidden Phrases
|
|
4
|
+
|
|
5
|
+
Never use these AI-signature phrases:
|
|
6
|
+
- "Let's dive in" / "Let's explore"
|
|
7
|
+
- "Here's a breakdown" / "Here's what you need to know"
|
|
8
|
+
- "In conclusion" / "To summarize"
|
|
9
|
+
- "It's worth noting" / "It's important to note"
|
|
10
|
+
- "At the end of the day"
|
|
11
|
+
- "Moving forward"
|
|
12
|
+
- "That being said"
|
|
13
|
+
- "Without further ado"
|
|
14
|
+
- "Game-changer"
|
|
15
|
+
- "Take it to the next level"
|
|
16
|
+
- "Unlock the potential"
|
|
17
|
+
- "In today's fast-paced world"
|
|
18
|
+
|
|
19
|
+
## Forbidden Words — Use Instead
|
|
20
|
+
|
|
21
|
+
| Forbidden | Use Instead |
|
|
22
|
+
|-----------|-------------|
|
|
23
|
+
| leverage | use, apply, build on |
|
|
24
|
+
| utilize | use |
|
|
25
|
+
| streamline | simplify, speed up, reduce steps |
|
|
26
|
+
| robust | reliable, solid, thorough |
|
|
27
|
+
| seamless | smooth, effortless, uninterrupted |
|
|
28
|
+
| cutting-edge | modern, current, recent |
|
|
29
|
+
| empower | enable, support, give tools |
|
|
30
|
+
| synergy | collaboration, combined effect |
|
|
31
|
+
| holistic | complete, full, comprehensive |
|
|
32
|
+
| actionable insights | practical recommendations |
|