@forwardimpact/outpost 3.12.0 → 3.13.0

package/templates/MIGRATION.md

@@ -0,0 +1,359 @@
+# Outpost Knowledge Base Migration
+
+This playbook moves a legacy knowledge base (`Knowledge/` wrapper plus a
+personal `Drafts/` directory) into root-level tiers. Agents execute the
+mechanical phases. You decide at four named gates. The validator arbitrates
+completion. Do not migrate by hand: a mature vault holds thousands of notes
+and more links than a person can rewrite correctly.
+
+## The safety model
+
+Follow these rules before any phase and during every phase:
+
+1. **Stop the agent scheduler.** Scheduled agents write into the vault on
+   short cycles. A migration that races a writer produces a hybrid layout.
+2. **Pause the sync client.** A mass rename inside a synced folder creates
+   conflicts and deletes files on teammates' replicas.
+3. **Work on a copy.** Copy the vault to a local directory that no sync
+   client watches. Dereference symlinks during the copy (`cp -RL`). Exclude
+   dependency directories, nested repositories, and files that hold
+   credentials.
+4. **Put the copy under version control.** Run `git init` and commit the
+   baseline. Commit at every phase boundary with the phase name. This is
+   your rollback path inside the copy.
+5. **Do not touch the live share until cutover.** All phases except cutover
+   run in the copy.
+6. **Narrowing is not un-sharing.** Moving a note to a narrower tier stops
+   future disclosure. It does not retract what recipients already read, and
+   the sync platform's version history may retain the old content. Where
+   past disclosure matters, use the platform's history controls; they are
+   outside Outpost's scope.
+
+## The phases
+
+Run the phases in order. Each phase has an exit test. Do not start a phase
+before the previous exit test passes.
+
+### Phase 0 — Freeze
+
+Stop the scheduler. Pause sync. Make the working copy. Commit the baseline.
+
+*Exit test:* no process writes into the vault or the copy; the baseline
+commit exists.
+
+### Phase 1 — Inventory (Gate 1: the tier map)
+
+An agent walks the copy and produces a census:
+
+- every top-level directory under the legacy wrapper, including the ones
+  the template never shipped (installations grow their own entity types);
+- link statistics per directory pair, so you see which flows a tier split
+  would cut;
+- duplicate basenames, duplicate identity files, and dangling links;
+- every existing frontmatter key with its value shapes, every inline
+  bold-key Info field with its occurrence count, and every hashtag-shaped
+  token (most tokens are noise: hex colors, ticket identifiers, and UUID
+  fragments);
+- every personal root entry, so tooling knows what it must never touch;
+- a **proposed tier map**: one tier per top-level directory, with the link
+  evidence for each proposal.
+
+**Gate 1 — you approve the tier map.** Migration blocks until every
+top-level knowledge directory has an assigned tier. Commit the approved map
+as the migration manifest; every later phase consumes it. The manifest also
+carries three stamping maps built from the census: the directory-to-type
+map (one `type` value per top-level directory), the status-variant map
+(every observed free-text status value, mapped onto the registry vocabulary
+or marked for the review queue), and the drift map (every observed
+frontmatter key spelling, every ad-hoc `type` value, and every inline
+Info-line key, each mapped onto one registry key or value, or marked to
+stay body prose). The maps sit at this gate for one reason: Phase 3 stamps
+frontmatter from them, so a later approval would block the mechanical pass.
+Recurring hard cases:
+
+- Per-person goal notes: no tier expresses "the person plus their manager."
+  Default them narrow; share by export.
+- Deliverables addressed to named recipients: tier 0 plus export, never a
+  shared-tier placement.
+- Asset and reference collections: the tier follows the audience. Mark
+  third-party copies and licensed assets no-redistribute; they are
+  ineligible for the public tier whatever their audience.
+
+*Exit test:* the manifest maps every directory to a tier and a type; the
+status and drift maps cover every observed variant; the census is
+committed.
+
+### Phase 2 — Hygiene
+
+An agent fixes what would fail validation for reasons older than the
+migration: merge duplicate identity notes, delete ingestion debris, and
+resolve dangling links. A dangling link that is correct by design (a
+scheduled skill mints links ahead of the target) goes on the proposed
+baseline list instead.
+
+*Exit test:* the only unresolved links left are on the proposed baseline
+list.
+
+### Phase 3 — Mechanical move and rewrite
+
+Agents execute the manifest:
+
+- create the tier directories at the root;
+- move each top-level directory into its assigned tier; move folder-atomic
+  units (a per-entity subdirectory, an asset collection, a note with its
+  dataset) as single units, never split below folder level;
+- rewrite every wiki link to the tier-prefixed, vault-absolute form and
+  convert every bare-basename link; keep display aliases; handle
+  escaped-pipe aliases inside tables, links inside front matter,
+  markdown-style relative links, URL-encoded links, and links to binary
+  targets. The rewriter and the stamper must cover every construct the
+  validator's link and frontmatter checks flag, or convergence never ends;
+- leave relative links inside one entity subdirectory untouched;
+- rewrite literal path strings and embedded commands that name legacy
+  paths, not only link syntax;
+- stamp frontmatter in the same pass, with the deterministic rules below,
+  so two different agents produce byte-identical blocks on the same note:
+  - fix one run date when Phase 3 starts and pass it to every shard;
+    every date fallback below uses that fixed date, whatever day a shard
+    runs on;
+  - stamp `type` from the approved directory-to-type map; never guess;
+  - stamp `created` with the oldest date in the note's dated activity or
+    pipeline bullets; accept both bullet grammars (a bold date with a
+    source label, and a plain date); when the note has no dated bullet,
+    use the fixed run date;
+  - stamp `updated` with the newest such date, with the same fallback;
+  - lift the inline Aliases field into the `aliases` list, add the
+    reversed name-order variant (split the basename on its first comma
+    and swap the two parts; skip the variant when the basename holds no
+    comma or when the `type` is organization), deduplicate exact matches,
+    and remove the lifted line;
+  - lift every `**Key:** value` Info line whose key the approved drift
+    map names into its property (`email`, `role`, `organization`,
+    `status` through the status-variant map, `location`, `first_seen`,
+    `last_seen`, `source`); match keys through the drift map only, never
+    by guess; remove each lifted line; leave every unmapped bold key as
+    body prose;
+  - stamp `date` and `period` on briefing files from the filename;
+  - normalize the small legacy frontmatter batch through the drift map:
+    unify spelling-variant keys to one key, collapse the source-key
+    variants to `source`, and remap ad-hoc `type` values; a key or value
+    the drift map does not cover joins the review queue;
+  - rewrite wiki links inside frontmatter values in the same pass as body
+    links, quoted and vault-absolute (the syntax matrix already names
+    front-matter links);
+  - write the canonical key order, so every stamped block is byte-stable;
+- move the draft-status ID ledgers (`Drafts/handled`, `Drafts/ignored`) to
+  `~/.cache/fit/outpost/drafts/` and verify the entry counts match.
+
+The stamping pass touches nearly every file. That churn is one more reason
+every phase runs in the version-controlled copy, with the scheduler
+stopped, and never in the live share.
+
+*Exit test:* the legacy wrapper and the old drafts directory are empty and
+deleted in the copy; the validator reports no legacy-layout finding; no
+shared-tier note lacks its required keys; a note the stamper cannot
+complete joins the review queue.
+
+### Phase 4 — Surgical split (Gate 2: narrow routing)
+
+This phase is the reason the migration exists. Content does not only move;
+it splits. An agent triages every note above a size threshold and every
+note that matches sensitivity markers (compensation figures, requisition
+identifiers, succession language) into a review queue, then **proposes**
+splits using the deterministic rules below. Agents propose; you approve.
+
+**The split rules:**
+
+1. **Facet overlay.** A sensitive facet of an entity moves to an overlay
+   note in the narrower tier. The overlay declares itself by its one-way
+   link to the canonical note. The same relative path is the default; a
+   cross-entity overlay uses an explicit link instead. Stamp the overlay
+   with `canonical`: a quoted, tier-prefixed, vault-absolute link to the
+   canonical note. Add one audience-labeled alias. A cross-entity overlay
+   keeps its own `type`.
+2. **Timeline split.** When sensitivity interleaves per dated entry inside
+   one activity log, the canonical note keeps the wide-audience entries and
+   the overlay holds the narrower entries under the same date keys. A
+   narrow-access reader merges the two logs chronologically. Stamp the
+   overlay as in rule 1.
+3. **Link inversion.** A wider note's link into a narrower tier moves, with
+   its one-line context, into the narrower note. Leave no tombstone and no
+   forwarding prose in the wider note.
+4. **Inverse stub.** When a note is narrow in its entirety but widely
+   linked, create a wider-tier stub that carries only shareable identity
+   facts. The narrow note links down to the stub. The narrow note is the
+   overlay: stamp it as in rule 1, with `canonical` pointing at the stub.
+5. **Hire conversion.** When a recruitment subject joins the team, create
+   the team-tier note fresh. The recruitment record stays in its tier and
+   links up. Nothing links back down. Stamp the candidate note with the
+   `person` property: a quoted link up to the fresh team-tier note. The
+   person note carries no link back.
+6. **Detach before promoting.** A note headed for the public tier first
+   loses or inlines its internal links, and passes the rights check.
+
+**Gate 2 — you approve every routing into tier 1 or tier 0.** No agent
+decides alone that content is management-only or owner-only. The gate does
+not grow with the frontmatter work: audience decisions stay its only
+subject, and the overlay stamps are mechanical.
+
+*Exit test:* the review queue is empty; every approved split is applied and
+committed.
+
+### Phase 5 — Convergence (Gate 3: the baseline)
+
+Run the validator in machine-readable mode in a loop. Partition each
+finding: **mechanical** (the rewriter fixes it), **judgment** (append to
+the review queue and return to phase 4), or **grandfathered** (append to
+the baseline with a one-line reason). Frontmatter findings
+(`frontmatter-missing`, `frontmatter-invalid`, `frontmatter-vocabulary`,
+`overlay-undeclared`) partition the same way and enter the same baseline.
+A metadata gap the stamper can fill is mechanical; it is never baselined.
+A gap that needs a human fact goes to the review queue or onto the
+baseline with a one-line reason. Examples: an unmappable status value, an
+ambiguous alias, and a legitimate same-name duplicate flagged as
+`overlay-undeclared`. Baseline keys are kind, file, and property, plus
+value for vocabulary findings, never line. Later edits therefore do not
+resurface grandfathered entries. Iterate until findings minus baseline
+is empty.
+
+**Gate 3 — you approve the baseline.** You approve the frontmatter entries
+together with the link entries. Commit it as `validation-baseline.json` at
+the vault root, so
+every post-migration regression is a new finding, not noise.
+
+A green validator proves structure, not content. Before the first share,
+read through every note above the size threshold once: sensitive facts also
+occur as plain prose that no link check can see.
+
+*Exit test:* validation passes with the approved baseline; the content
+audit is done.
+
+### Phase 6 — Repoint
+
+Rewrite every surface that writes into the vault, or the legacy layout
+regrows on the next scheduled run:
+
+- run `npx fit-outpost update` to install the tier-aware instructions;
+- carry your local edits over: agent profiles, skill configuration,
+  embedded search commands inside notes, ignore rules (match case
+  exactly), and editor configuration;
+- retarget every external generator and ingestion pipeline at the new tier
+  paths;
+- verify every generator and skill emits conforming frontmatter: the
+  canonical key order, registry values, and quoted links;
+- start one fresh changelog per shared tier; move the legacy changelog,
+  whole, into the narrowest tier its entries span, fix its inbound links,
+  and never append to it again. The root instruction changelog is a
+  different artifact and stays where it is.
+
+*Exit test:* a dry-run agent session writes only tier-prefixed paths with
+conforming frontmatter.
+
+### Phase 7 — Cutover (Gate 4: the shares)
+
+Sharing is per tier and cumulative. Folder permissions cannot express
+"tier N and every wider tier" by inheritance, so use groups:
+
+1. Per shared tier, create the cloud folder or Git remote. For Git, use one
+   repository per shared tier, never one repository that spans tiers:
+   history would carry narrow content into wide clones.
+2. Per shared tier, create one group. A tier-N member joins the groups for
+   tier N through the widest tier. Revocation removes the member from all
+   of them.
+3. Let each folder sync locally, then symlink it into the vault root under
+   its rank-prefixed name. The sync target's own name does not matter.
+4. Copy the migrated content in, widest tier first. Recipients place each
+   received tier folder as a sibling under one local root, restore the
+   rank-prefixed name if their platform changed it, and run
+   `npx fit-outpost validate` on that root.
+5. Flip the legacy share to read-only. Retire it after a stated retention
+   window, once teammates confirm the new tiers sync.
+6. Restart the agent scheduler.
+
+**Gate 4 — you grant the ACLs.** The validator cannot check who a platform
+grants access to. Put a recurring audience audit on your calendar.
+
+*Exit test:* validation passes on the live vault; a recipient's suffix
+validates; the scheduler runs against tier paths only.
+
+## Appendix A — the migration workflow prompt
+
+Paste the prompt below into a Claude Code session at the root of the
+**working copy** (never the live share). Fill the two placeholders. The
+`ultracode` keyword opts the session into multi-agent orchestration; the
+migration then runs as staged workflows with the gates above as stopping
+points.
+
+```text
+ultracode
+
+Migrate this Outpost knowledge base from the legacy layout (Knowledge/
+wrapper plus Drafts/) to root-level tiers, following MIGRATION.md in this
+directory. The tier manifest is at <path-to-approved-manifest>. My review
+decisions go in <path-to-review-queue-file>. The property registry is
+`registry.yaml` at the vault root.
+
+Rules that bind every agent you spawn:
+- Work only inside this directory. Never follow symlinks out of it. Never
+  read or write personal root entries other than the files MIGRATION.md
+  names (instruction files, ignore rules, editor configuration).
+- Never decide an audience. Anything that routes into tier 1 or tier 0,
+  and every proposed split, goes into the review queue and stops there
+  until I mark it approved.
+- Commit at every phase boundary with the phase name. Never use
+  destructive git commands.
+- Apply the split rules from MIGRATION.md § Phase 4 exactly. Do not invent
+  alternative split shapes. Move the link plus its one-line context on
+  inversion; leave no tombstone.
+- The link rewriter and the validator must agree: cover aliased links,
+  escaped pipes inside tables, front-matter links, markdown relative
+  links, URL-encoded links, binary targets, and literal path strings. The
+  stamper and the frontmatter checks must agree the same way, or
+  convergence never ends.
+- Stamp frontmatter only from the approved manifest maps and
+  `registry.yaml`. Apply the stamping rules from MIGRATION.md § Phase 3
+  exactly. Never invent a key, a type value, a status value, or
+  a tag. Lifted Info lines leave the body.
+- Folder-atomic units move whole. Never split below folder level.
+
+Run these workflows in order, and stop for my gate review between them:
+1. Inventory: fan out readers per top-level directory; produce the census
+   and the proposed tier map with link evidence; include the metadata
+   census and propose the directory-to-type map and the status-variant
+   map. Stop for Gate 1.
+2. Hygiene: merge duplicate identities, fix dangling links, list
+   by-design dangles for the baseline.
+3. Move and rewrite: execute the approved manifest; shard the link
+   rewrite by directory across parallel agents; run the stamping pass in
+   the same shards; verify with a full-vault link resolution pass.
+4. Split: triage notes above the size threshold and notes matching
+   sensitivity markers; per flagged note, one splitter agent proposes the
+   split and an independent reviewer agent verifies it against the split
+   rules; write proposals to the review queue. Stop for Gate 2, then
+   apply only approved proposals.
+5. Convergence: loop `npx fit-outpost validate` in JSON mode; auto-fix
+   mechanical findings; queue judgment findings; propose baseline
+   entries. Stop for Gate 3.
+6. Repoint: rewrite instruction surfaces, embedded commands, ignore
+   rules, and generator configuration; prove with a dry-run session that
+   writes only tier-prefixed paths with conforming frontmatter.
+
+Then hand back a migration report: what moved where, every split applied,
+the final baseline, and the cutover checklist from MIGRATION.md § Phase 7
+for me to execute against the sync platform.
+```
+
+## Appendix B — what the validator will and will not tell you
+
+- It proves ranks, link direction, link resolution, and link format. It
+  follows symlinked tiers.
+- On frontmatter, it proves the required keys, the closed vocabularies,
+  the tag grammar and tier bounds, and property-link legality. It does not
+  prove the freshness of `updated`, the completeness of `aliases`, the
+  truth of a `status`, or the retrieval quality of a tag. Instructions and
+  the content audit own those.
+- It does not prove prose is audience-appropriate, and it cannot see the
+  sync platform's permissions. The content audit (phase 5) and the
+  audience audit (gate 4) own those.
+- After migration, a legacy-layout finding means a writer you did not
+  repoint still produces old paths. Fix the writer, not the finding.

package/templates/registry.yaml

@@ -0,0 +1,25 @@
+# Metadata vocabularies for this knowledge base. Humans edit this file;
+# agents only select from it. See CLAUDE.md § Note Metadata for the rules.
+types: # directory name -> type value
+  People: person
+  Organizations: organization
+  Projects: project
+  Topics: topic
+  Teams: team
+  Candidates: candidate
+  Prospects: prospect
+  Roles: role
+  Priorities: priority
+  Conditions: condition
+  Tasks: task
+  Erasure: erasure
+reserved: # file basenames with a fixed type, in any tier
+  CHANGELOG.md: changelog
+status: # per-type closed vocabularies
+  candidate: [new, screening, interviewing, offer, hired, rejected, withdrawn]
+  prospect: [identified, contacted, responded, converted, closed]
+tags: # closed topic/ taxonomy; bound = the widest tier a tag may reach
+  - { tag: topic/hiring, bound: 2, intent: recruitment pipeline retrieval }
+  - { tag: topic/planning, bound: 3, intent: project and priority retrieval }
+rights:
+  - no-redistribute

package/templates/.claude/skills/anarlog-follow/scripts/follow.mjs

@@ -1,243 +0,0 @@
-#!/usr/bin/env bun
-
-/**
- * follow.mjs — Read a live Anarlog transcript and output new content since
- * the last read. Designed to be called repeatedly during a live session.
- *
- * Usage:
- *   node follow.mjs <session-id>                    # First read — outputs everything
- *   node follow.mjs <session-id> --after <word-id>  # Outputs words after the given word ID
- *   node follow.mjs <session-id> --after <word-id> --summary  # Condensed summary mode
- *   node follow.mjs <session-id> --meta              # Output session metadata only
- *   node follow.mjs --detect                          # Detect the most recently active session
- *
- * Output (JSON):
- *   {
- *     "session_id": "...",
- *     "title": "...",
- *     "total_words": 1234,
- *     "new_words": 56,
- *     "last_word_id": "...",
- *     "duration_ms": 123456,
- *     "channels": {
- *       "0": { "label": "user", "word_count": 600 },
- *       "1": { "label": "guest", "word_count": 634 }
- *     },
- *     "text": [
- *       { "channel": 0, "start_ms": 1000, "end_ms": 5000, "text": "Hello, how are you?" },
- *       ...
- *     ]
- *   }
- */
-
-import { readFileSync, readdirSync, statSync } from "node:fs";
-import { join } from "node:path";
-import { homedir } from "node:os";
-
-const SESSIONS_DIR = join(
-  homedir(),
-  "Library/Application Support/anarlog/sessions",
-);
-
-function parseArgs() {
-  const args = process.argv.slice(2);
-  const flags = {};
-  let positional = null;
-
-  for (let i = 0; i < args.length; i++) {
-    if (args[i] === "--after" && i + 1 < args.length) {
-      flags.after = args[++i];
-    } else if (args[i] === "--summary") {
-      flags.summary = true;
-    } else if (args[i] === "--meta") {
-      flags.meta = true;
-    } else if (args[i] === "--detect") {
-      flags.detect = true;
-    } else if (!args[i].startsWith("--")) {
-      positional = args[i];
-    }
-  }
-
-  return { sessionId: positional, ...flags };
-}
-
-function detectActiveSession() {
-  const entries = readdirSync(SESSIONS_DIR);
-  let best = null;
-  let bestMtime = 0;
-
-  for (const entry of entries) {
-    const transcriptPath = join(SESSIONS_DIR, entry, "transcript.json");
-    try {
-      const stat = statSync(transcriptPath);
-      if (stat.mtimeMs > bestMtime) {
-        bestMtime = stat.mtimeMs;
-        best = entry;
-      }
-    } catch {
-      // No transcript — skip
-    }
-  }
-
-  if (!best) {
-    console.error("No active Anarlog session found.");
-    process.exit(1);
-  }
-
-  // Check if the transcript was modified recently (within last 5 minutes)
-  const ageMs = Date.now() - bestMtime;
-  const isLive = ageMs < 5 * 60 * 1000;
-
-  const metaPath = join(SESSIONS_DIR, best, "_meta.json");
-  let title = "Unknown";
-  try {
-    const meta = JSON.parse(readFileSync(metaPath, "utf-8"));
-    title = meta.title || "Untitled";
-  } catch {
-    // No meta
-  }
-
-  return {
-    session_id: best,
-    title,
-    is_live: isLive,
-    last_modified: new Date(bestMtime).toISOString(),
-    age_seconds: Math.round(ageMs / 1000),
-  };
-}
-
-function readMeta(sessionId) {
-  const metaPath = join(SESSIONS_DIR, sessionId, "_meta.json");
-  try {
-    return JSON.parse(readFileSync(metaPath, "utf-8"));
-  } catch {
-    return { title: "Unknown", created_at: null, participants: [] };
-  }
-}
-
-function readTranscript(sessionId) {
-  const path = join(SESSIONS_DIR, sessionId, "transcript.json");
-  try {
-    const data = JSON.parse(readFileSync(path, "utf-8"));
-    return data.transcripts?.[0]?.words || [];
-  } catch {
-    return [];
-  }
-}
-
-function groupIntoSegments(words) {
-  if (words.length === 0) return [];
-
-  const segments = [];
-  let current = {
-    channel: words[0].channel,
-    start_ms: words[0].start_ms,
-    end_ms: words[0].end_ms,
-    texts: [words[0].text],
-  };
-
-  for (let i = 1; i < words.length; i++) {
-    const w = words[i];
-    const gap = w.start_ms - current.end_ms;
-
-    // New segment on channel change or >3s gap
-    if (w.channel !== current.channel || gap > 3000) {
-      segments.push({
-        channel: current.channel,
-        start_ms: current.start_ms,
-        end_ms: current.end_ms,
-        text: current.texts.join("").trim(),
-      });
-      current = {
-        channel: w.channel,
-        start_ms: w.start_ms,
-        end_ms: w.end_ms,
-        texts: [w.text],
-      };
-    } else {
-      current.end_ms = w.end_ms;
-      current.texts.push(w.text);
-    }
-  }
-
-  // Push final segment
-  segments.push({
-    channel: current.channel,
-    start_ms: current.start_ms,
-    end_ms: current.end_ms,
-    text: current.texts.join("").trim(),
-  });
-
-  return segments.filter((s) => s.text.length > 0);
-}
-
-function buildChannelStats(allWords) {
-  const channels = {};
-  for (const w of allWords) {
-    if (!channels[w.channel]) {
-      channels[w.channel] = {
-        label: w.channel === 0 ? "user" : `guest-${w.channel}`,
-        word_count: 0,
-      };
-    }
-    channels[w.channel].word_count++;
-  }
-  return channels;
-}
-
-function filterNewWords(allWords, afterId) {
-  if (!afterId) return allWords;
-  const idx = allWords.findIndex((w) => w.id === afterId);
-  // If word ID not found, return everything (safety fallback)
-  return idx >= 0 ? allWords.slice(idx + 1) : allWords;
-}
-
-function main() {
-  const opts = parseArgs();
-
-  // Detect mode
-  if (opts.detect) {
-    console.log(JSON.stringify(detectActiveSession(), null, 2));
-    return;
-  }
-
-  if (!opts.sessionId) {
-    console.error(
-      "Usage: follow.mjs <session-id> [--after <word-id>] [--meta]",
-    );
-    process.exit(1);
-  }
-
-  const meta = readMeta(opts.sessionId);
-
-  // Meta-only mode
-  if (opts.meta) {
-    console.log(JSON.stringify(meta, null, 2));
-    return;
-  }
-
-  // Read transcript
-  const allWords = readTranscript(opts.sessionId);
-  const words = filterNewWords(allWords, opts.after);
-  const lastWord = allWords[allWords.length - 1];
-
-  console.log(
-    JSON.stringify(
-      {
-        session_id: opts.sessionId,
-        title: meta.title,
-        created_at: meta.created_at,
-        total_words: allWords.length,
-        new_words: words.length,
-        last_word_id: lastWord?.id || null,
-        duration_ms: lastWord?.end_ms || 0,
-        channels: buildChannelStats(allWords),
-        text: groupIntoSegments(words),
-      },
-      null,
-      2,
-    ),
-  );
-}
-
-main();