@gcunharodrigues/wrxn 0.1.0

package/payload/.wrxn/wiki.cjs

@@ -0,0 +1,164 @@
+#!/usr/bin/env node
+'use strict';
+
+// WRXN memory-wiki adapter — the install-local CLI over the file-based memory tiers.
+// Self-contained: this ships INTO an install and MUST NOT import the kernel lib (node stdlib only).
+//
+// Tiers live under <installRoot>/.wrxn/wiki/<tier>/ where tier ∈ {concepts, decisions, gotchas, sessions}.
+// Each page is a plain markdown file. Empty tiers are the fresh-install default — every read path
+// must return cleanly (no crash) over an empty wiki.
+//
+// Subcommands:
+//   query <text...>              grep-style substring search → JSON {query, tier, total, hits[]}
+//   recall <text...>             alias of query (page-level recall; same substring engine)
+//   write-page <tier> <slug>     create <tier>/<slug>.md (refuses to overwrite); prints the path
+//
+// Flags: --tier <concepts|decisions|gotchas|sessions|all> (default all) · --limit <N> (default 20)
+//        --root <dir> (override the install-root walk-up; mainly for tests)
+
+const fs = require('fs');
+const path = require('path');
+
+const TIERS = ['concepts', 'decisions', 'gotchas', 'sessions'];
+
+// ── install-root resolution (walk up to the wrxn.install.json receipt) ────────
+// Mirrors payload/.claude/hooks/enforce-managed-guard.cjs findInstallRoot.
+function findInstallRoot(start) {
+  let dir = start || process.env.CLAUDE_PROJECT_DIR || process.cwd();
+  for (let i = 0; i < 12; i++) {
+    if (fs.existsSync(path.join(dir, 'wrxn.install.json'))) return dir;
+    const up = path.dirname(dir);
+    if (up === dir) break;
+    dir = up;
+  }
+  return null;
+}
+
+function flag(name) {
+  const i = process.argv.indexOf(`--${name}`);
+  return i > -1 ? process.argv[i + 1] : undefined;
+}
+
+function wikiRoot() {
+  const override = flag('root');
+  const root = override || findInstallRoot();
+  if (!root) {
+    fail('cannot resolve the install root — run inside a wrxn install (no wrxn.install.json found walking up) or pass --root <dir>');
+  }
+  return path.join(root, '.wrxn', 'wiki');
+}
+
+function fail(msg) {
+  process.stderr.write(`wiki: ${msg}\n`);
+  process.exit(2);
+}
+
+// positional args after the subcommand, up to the first --flag
+function positionals() {
+  const out = [];
+  for (let i = 3; i < process.argv.length; i++) {
+    if (process.argv[i].startsWith('--')) break;
+    out.push(process.argv[i]);
+  }
+  return out;
+}
+
+function tierDirs(root, tierFlag) {
+  if (!tierFlag || tierFlag === 'all') return TIERS.map((t) => [t, path.join(root, t)]);
+  if (!TIERS.includes(tierFlag)) fail(`unknown tier "${tierFlag}" — one of ${TIERS.join(', ')}, all`);
+  return [[tierFlag, path.join(root, tierFlag)]];
+}
+
+function listPages(dir) {
+  let names;
+  try {
+    names = fs.readdirSync(dir);
+  } catch {
+    return []; // tier dir absent → empty, no crash
+  }
+  return names.filter((n) => n.endsWith('.md')).map((n) => path.join(dir, n));
+}
+
+// ── query / recall (shared substring engine) ─────────────────────────────────
+function runQuery() {
+  const terms = positionals();
+  if (terms.length === 0) {
+    process.stdout.write('Usage: node .wrxn/wiki.cjs query <search-term...> [--tier all|concepts|decisions|gotchas|sessions] [--limit N]\n');
+    process.exit(2);
+  }
+  const needle = terms.join(' ').toLowerCase();
+  const tierFlag = flag('tier') || 'all';
+  const limit = Number(flag('limit')) || 20;
+  const root = wikiRoot();
+
+  const hits = [];
+  for (const [tier, dir] of tierDirs(root, tierFlag)) {
+    for (const file of listPages(dir)) {
+      const lines = fs.readFileSync(file, 'utf8').split('\n');
+      for (let n = 0; n < lines.length; n++) {
+        if (lines[n].toLowerCase().includes(needle)) {
+          hits.push({ tier, file: path.relative(root, file), line: n + 1, snippet: lines[n].trim() });
+          if (hits.length >= limit) break;
+        }
+      }
+      if (hits.length >= limit) break;
+    }
+    if (hits.length >= limit) break;
+  }
+
+  process.stdout.write(
+    JSON.stringify({ query: terms.join(' '), tier: tierFlag, total: hits.length, returned: hits.length, hits }, null, 2) + '\n'
+  );
+}
+
+// ── write-page ────────────────────────────────────────────────────────────────
+function runWritePage() {
+  const [tier, slug] = positionals();
+  if (!tier || !slug) {
+    process.stdout.write('Usage: node .wrxn/wiki.cjs write-page <tier> <slug> [--description "..."] [--body "..."]\n');
+    process.exit(2);
+  }
+  if (!TIERS.includes(tier)) fail(`unknown tier "${tier}" — one of ${TIERS.join(', ')}`);
+  if (!/^[a-z0-9][a-z0-9-]*$/.test(slug)) fail(`slug must be kebab-case ([a-z0-9-]): "${slug}"`);
+
+  const root = wikiRoot();
+  const dir = path.join(root, tier);
+  fs.mkdirSync(dir, { recursive: true });
+  const dest = path.join(dir, `${slug}.md`);
+  if (fs.existsSync(dest)) fail(`page already exists, refusing to overwrite: ${path.relative(root, dest)}`);
+
+  const description = flag('description') || '';
+  const body = flag('body') || '';
+  const page = [
+    '---',
+    `name: ${slug}`,
+    `description: ${description}`,
+    `tier: ${tier}`,
+    'source: wiki-cli-write-page',
+    '---',
+    '',
+    `# ${slug}`,
+    '',
+    body,
+    '',
+  ].join('\n');
+
+  fs.writeFileSync(dest, page);
+  process.stdout.write(JSON.stringify({ written: path.relative(root, dest), tier }, null, 2) + '\n');
+}
+
+function main() {
+  const cmd = process.argv[2];
+  switch (cmd) {
+    case 'query':
+    case 'recall':
+      return runQuery();
+    case 'write-page':
+      return runWritePage();
+    default:
+      process.stdout.write('Usage: node .wrxn/wiki.cjs <query|recall|write-page> ...\n');
+      process.exit(cmd ? 2 : 0);
+  }
+}
+
+main();

package/payload/aios-intake.md

@@ -0,0 +1,32 @@
+# AIS-OS intake
+
+The canonical operator intake. Fill each answer, then run `wrxn onboard` (or the `onboard` skill) to
+scaffold your Day-1 operator file set under `context/`. Idempotent — edit and re-run any time.
+
+## Q1 — Who are you, what do you sell, who do you sell it to?
+
+[Your answer here]
+
+## Q2 — Paste 1-2 things you've written recently (raw, unedited — voice samples)
+
+[Your answer here]
+
+## Q3 — Your 2-3 biggest priorities for the next 90 days
+
+[Your answer here]
+
+## Q4 — Where does revenue land, and where is it tracked?
+
+[Your answer here]
+
+## Q5 — Where do you talk to customers, your team, and the outside world?
+
+[Your answer here]
+
+## Q6 — Where do recordings, notes, and important docs live?
+
+[Your answer here]
+
+## Q7 — The one task that eats your week, and where you track work
+
+[Your answer here]

package/payload/connections.md

@@ -0,0 +1,15 @@
+# Connections registry
+
+Every system your AIOS can reach — the single source of truth for what's wired in. Add a row when you
+connect a tool; `level-up` and `audit` read this to find gaps.
+
+| System | Category | Status | Notes |
+|--------|----------|--------|-------|
+| _(none yet)_ | | | run `wrxn onboard` / the onboard skill to seed this from your intake |
+
+## Categories (the Four-Cs domains)
+
+- **Capture** — where work + ideas land (tasks, notes, docs)
+- **Communicate** — email, chat, DMs, calendar
+- **Convert** — revenue, CRM, billing
+- **Coordinate** — team, recordings, automation

package/payload/decisions/log.md

@@ -0,0 +1,18 @@
+# Decisions Log
+
+Append-only record of meaningful decisions and why they were made. Append whenever you decide
+something worth remembering; `level-up` Phase 2 also writes scoped automation specs here.
+
+**Format per entry:**
+
+```
+## YYYY-MM-DD — <short title>
+
+**Decision:** <what was decided>
+**Why:** <the reasoning / what it rules out>
+**Revisit:** <when/what would change this>
+```
+
+---
+
+<!-- entries below, newest first -->

package/payload/docs/agents/domain.md

@@ -0,0 +1,38 @@
+# Domain Docs
+
+How the engineering skills should consume this repo's domain documentation when exploring the codebase.
+
+## Before exploring, read these
+
+- **`CONTEXT.md`** at the repo root, or
+- **`CONTEXT-MAP.md`** at the repo root if it exists — it points at one `CONTEXT.md` per context. Read each one relevant to the topic.
+- **`docs/adr/`** — read ADRs that touch the area you're about to work in. In multi-context repos, also check `src/<context>/docs/adr/` for context-scoped decisions.
+
+If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The producer skill (`grill-with-docs`) creates them lazily when terms or decisions actually get resolved.
+
+## File structure
+
+This install uses a **single-context** layout (most repos): one `CONTEXT.md` + `docs/adr/` at the repo root.
+
+```
+/
+├── CONTEXT.md
+├── docs/adr/
+│   ├── 0001-event-sourced-orders.md
+│   └── 0002-postgres-for-write-model.md
+└── src/
+```
+
+If this grows into a monorepo with separate contexts, add a `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files and the skills will switch to multi-context mode.
+
+## Use the glossary's vocabulary
+
+When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
+
+If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `grill-with-docs`).
+
+## Flag ADR conflicts
+
+If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
+
+> _Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_

package/payload/docs/agents/issue-tracker.md

@@ -0,0 +1,25 @@
+# Issue tracker: Local Markdown
+
+Issues and PRDs for this repo live as markdown files in `.scratch/`. This is the
+WRXN kernel default — a tracker that needs no remote and no `gh`/`glab` CLI.
+
+## Conventions
+
+- One feature per directory: `.scratch/<feature-slug>/`
+- The PRD is `.scratch/<feature-slug>/PRD.md`
+- Implementation issues are `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`
+- Triage state is recorded as a `Status:` line near the top of each issue file (see `triage-labels.md` for the role strings)
+- Comments and conversation history append to the bottom of the file under a `## Comments` heading
+
+## When a skill says "publish to the issue tracker"
+
+Create a new file under `.scratch/<feature-slug>/` (creating the directory if needed).
+
+## When a skill says "fetch the relevant ticket"
+
+Read the file at the referenced path. The user will normally pass the path or the issue number directly.
+
+## Switching trackers
+
+To use GitHub or GitLab issues instead, re-run `setup-matt-pocock-skills` and pick the
+matching tracker — it will rewrite this file from the right template.

package/payload/docs/agents/triage-labels.md

@@ -0,0 +1,15 @@
+# Triage Labels
+
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
+
+| Canonical role    | Label in our tracker | Meaning                                  |
+| ----------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`    | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`      | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent` | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human` | `ready-for-human`    | Requires human implementation            |
+| `wontfix`         | `wontfix`            | Will not be actioned                     |
+
+When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
+
+In the local-markdown tracker (the kernel default), the "label" is the `Status:` line at the top of the issue file. Edit the right-hand column to match whatever vocabulary you actually use.

package/payload/docs/workspace/operator-layer.md

@@ -0,0 +1,14 @@
+# Operator Layer (workspace profile)
+
+This file is laid ONLY by a `wrxn init --workspace` install — it is the representative marker of
+the **workspace profile**. A `--project` install never receives it.
+
+The workspace profile = the project profile (dev pipeline + intelligence layer + enforcement
+boundary) **plus** the operator layer:
+
+- onboarding + the decisions log
+- the audit / level-up operating rituals
+- the connections registry (the workspace nervous system — `wrxn connect`; see issue 21)
+
+Project installs are the floor; workspace installs are the superset. This is a seeded file —
+yours to edit; `wrxn update` never overwrites it.