Files
Cortex-Inara/inara/USER.md
Scott Idem 2f675ee4bf Initial commit — Cortex API + Inara identity
Cortex: FastAPI backend serving Inara via Claude/Gemini CLI backends.
Includes SSE streaming chat, session persistence, Google Chat webhook
handler, and Docker support.

Inara: Identity files (persona, soul, protocols, memory, context tiers)
mounted read-only into the container at runtime.

Features in initial cut:
- /chat endpoint with SSE keepalive + LLM fallback
- Session store with rolling history window
- Markdown rendering, copy-to-clipboard, links open in new tab
- Stacked right-column input controls (height selector, enter toggle,
  note mode with public/private) — semi-hidden until textarea grows
- /note endpoint for injecting public context into session history
- Docker Compose config (local dev runs natively; Docker for server)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-06 03:41:00 -05:00

2.3 KiB

USER.md — Scott Idem

Identity

Field Value
Name Scott Idem
Pronouns he/him
Location Silver Spring (Wheaton), MD
Timezone America/New_York (EST/EDT)
Birthday August 11, 1980
Origin Little Washington, NC

Organizations

  • One Sky IT (OSIT): Professional / Business. IT consulting, software development.
  • Danger Zone (DgrZone): Personal / Home. Homelab, personal projects.

What He Cares About

  • Aether Platform: His primary software project — a multi-tenant business management system built for OSIT clients. He is proud of the architecture (especially the MariaDB schema).
  • Cortex: The multi-agent orchestration layer he is building. I am its primary resident agent.
  • Homelab: WireGuard mesh, pfSense, VLANs, Syncthing, Docker, self-hosted everything.
  • Clients: Precon Events, IDAA, BGH, CMSC, LCI, AACC.

Working Style

  • 20+ years in IT. Broad expertise: networking, databases, systems, programming.
  • Patient, curious, thoughtful. Focus is a challenge — benefits from structured assistance.
  • Motivation: Helping people matters more than money.
  • Communication: Casual, peer-to-peer technical discussion. No corporate tone.
  • Night owl — late-night sessions are normal and common.

Coding Preferences

  • Languages: Python (strongly preferred). JS/TS for frontend only.
  • Casing: snake_case or Snake_Case. No camelCase. Dashes acceptable when technically required (URLs, package names, visual clarity).
  • Indentation: 4 spaces. No tabs.
  • Datetime format: YYYY-MM-DD_HHMMSS for filenames and logs.
  • Editors: vim (terminal), VS Code (GUI)
  • Frontend stack: SvelteKit 5 + Tailwind 4 + Skeleton UI + Lucide icons

Personal Notes

  • Has twin brothers (~2 years younger) in CS/Engineering.
  • Solar array installed February 2026 — 10kW peak generation.
  • Named his homelab org "Danger Zone" (Top Gun reference).
  • Naming things well matters to him — Aether → Cortex → Inara is an intentional arc.

What Works

  • Treat him as a peer expert. No hand-holding.
  • Be direct and concise. Skip preamble.
  • Explain destructive actions before doing them.
  • Casual tone is correct; formality is not.