Namaste Ji by Ayushman Dash

Docs / glossary.md · mirrored from the repo

Glossary

Status: operational reference. The domain + system vocabulary in one place, so the deep docs can stay terse. Terms link to their owning doc where one exists. Cross-refs use the decision IDs those docs define.

Product & content

  • Greeting / devotional asset — the product unit: a shareable image (Good-morning, festival, deity, blessing). Success = it gets sent (P-3).
  • Share-intent / forwardability — the in-app signal that a user tapped share/forward. The North Star. Measured aggregate and only up to the OS share-sheet (DIST DS-10, P-8).
  • temporal_class — timeless (evergreen base-load, recyclable) vs time_bound (event/festival spikes, campaign-windowed, retired at decay_until) (DIST DS-3).
  • Campaign window — promote_from → peak → decay_until for time-bound content; peaks on the user’s local day (DIST §6, CREATIVE-PLANE §10).
  • Circulation cap — de-prioritize a piece after N sends in a locale; anti-popularity supply control (DIST DS-5).
  • Novelty-to-user — distance from the user’s seen-set; a first-class ranking term (DIST DS-4/DS-5).
  • Rarity / anti-popularity — the more a piece has circulated, the less we surface it — the inverse of a popularity boost (DIST DS-5).
  • Diversity / coverage / ILD — variety of a served page; ILD = intra-list distance (mean pairwise embedding distance); coverage = distinct clusters/attributes present.
  • Event runway — personalized lead-up to an event: lead time = f(user affinity); staged sub-types (anticipation → preparation → day-of → afterglow) (FEED-LAB §11, FL-8).

Content pipeline

  • Brief — the executable Content Brief the Creative Head emits; a versioned Zod contract consumed one-at-a-time cold (CREATIVE-PLANE, CP-3).
  • Content Strategy (strategy@vN) — the single versioned strategy artifact (absorbs the brief; carries production and delivery) (CREATIVE-HEAD).
  • Shot — a brief expanded into a concrete “to-render” spec; has a deterministic shot_id and a status lifecycle (packages/catalog).
  • (Content) asset — a produced/rendered piece; content_id, r2_master_key, embedding_id, status; lives in the catalog spine.
  • Batch — an OpenAI Batch job tracked by a D1 batch table + Cron poller (render/embed phases).
  • Sample set — a small versioned set for spikes/QA before a full batch execution.
  • Caption-bridge — embedding the text side (caption + attribute tags) alongside the image for the multimodal space.
  • Heimdall — the QA/eval agent (Langfuse-prompt metrics + hard cultural veto + LLM-judge; smart sampling) (CONTENT-PRODUCTION).
  • Publish gate — the manual (for now) gate from staged → live (a scheduler agent later).
  • STAGED / quarantined — the holding status after embed, before QA/publish.
  • DLQ — dead-letter queue; the inbox for messages that exhaust retries.

Agents (the Kernel)

  • Kernel — the one reusable agent anatomy every agent instantiates (AK-1).
  • Manifest — the YAML config that is an agent: model, memory, tools, subagents[], stop{}, autonomy, prompts{}, schedule, scopes (AK-8, AP §9).
  • Orchestrator — the thin agent that plans + dispatches; never thickened (capability grows via subagents, AK-1).
  • Subagent-as-tool — a subagent invoked as a tool with {objective, params, stm_projection}, returning {artifact, lineage}; itself a Kernel instance (AK-4).
  • Context firewall — the rule that a subagent’s raw transcript never reaches the orchestrator; only distilled artifact + lineage cross (AK-4, P-20).
  • STM (working memory) — per-run scratchpad; orchestrator-owned, projected read-only to subagents, compacted on context pressure (AK-2).
  • LTM (long-term memory) — cross-run lessons in one MemoryPort store scoped by agent_id+domain; written append-only, consolidated offline on verified outcomes (AK-3, P-24).
  • Calibrated stop — stopping by marginal-gain/confidence/coverage/soft-cost; max_loops is only a backstop (AK-5, P-21).
  • Reflection — generate → critique → revise against a rubric, as a Workflow (AP §5).
  • Lineage — the signals/recalled-lessons trail on each return; read by the Control DO gate and graded by the learning loop; replaces user-facing citations (AK-4).
  • Consolidation agent / Catalog Steward — offline agents that reinforce/decay memory and maintain the Catalog View (ORCHESTRATION §3–4).
  • Creative Head · Content Director · Content Creator — the content-plane agent roster (strategy → shots → render/embed).

Platform & control

  • Two planes — headless execution plane (all business logic) vs the control plane (BO: UI + thin control API + mode state, no business logic) (ARCHITECTURE §3, P-10).
  • Catalog spine — the shared source of truth: D1 (metadata) · R2 (bytes) · Vectorize (one multimodal index) (D8, P-11).
  • Control DO — the authoritative Durable Object for autonomy: globalMode, per-stage stageMode, thresholds, kill switch; broadcasts over WebSocket (ARCHITECTURE §3, D5).
  • Autonomy modes — manual (no loop) · proposes (drafts, founder commits) · auto (ships low-risk, escalates low-confidence/veto-risk) (AK-6).
  • Ship vs escalate — the two flavours of stopping the Control DO gate produces (AK-6).
  • AI Gateway — the routing/cost/cache/log layer all model calls pass through; holds provider keys (BYOK).
  • Langfuse — prompt registry (name@label) + LLM tracing + eval datasets (AK-6).
  • Ports — ModelPort / EmbedderPort / VectorIndex: provider-agnostic interfaces (BO-2, P-12).
  • PII plane — the sensitive data tier (profiles, phone, behaviour): region-pinned, minimized, retention-bounded (DS-15, P-27/P-28).
  • Feed Lab — the BO playground to visualize embeddings, tune FeedPolicy, and simulate the feed (FEED-LAB.md).
  • FeedPolicy / OnboardingSignals / coldStartVector() — the versioned feed policy artifact, the onboarding-signal schema, and the shared prior-assembly function used by both Lab and serving (FL-1/FL-2/FL-10).
  • Taste vector — a recency/share-weighted aggregate of what a user engaged with, in the multimodal space; drives kNN candidate generation (DS-12).

Infra & ops

  • Alchemy — TypeScript IaC that provisions CF backing resources (adopt: true everywhere).
  • adopt — Alchemy taking over a resource created out-of-band instead of erroring.
  • CI-as-deployer — GitHub Actions + Wrangler are the only deploy path; Pages on Direct Upload (Git auto-build off) (CI-1).
  • Secrets Store — Cloudflare’s one-per-account secret system of record (default_secrets_store).
  • Cloudflare Access / Better Auth — BO perimeter auth / consumer self-hosted auth (D7).
  • Workers Paid / Universal SSL first-level — Queues+Vectorize need the paid plan; free SSL covers root + first-level subdomains only, so BO hosts stay first-level (bo-staging, bo) (CI-6).
  • Statsig — the deferred frontend-plane experimentation/flags/analytics layer (BO-6).