Current Focus

This document is a short current-focus view for NEXUS-EMERGING.

It is intentionally a derived operational summary, not the deepest source truth.

Use it to orient quickly, then go to the linked durable docs.

Active Work

  • keep strengthening the ingestion foundation
  • preserve provider artifacts and Codex capture as traceable acquisition inputs
  • normalize imported material into canonical append-only history
  • preserve provenance strongly enough to support reparsing and later reinterpretation
  • avoid forcing the final ontology too early
  • make repo-as-memory and agent-readability more explicit
  • support multiple concern lines from the foundation rather than collapsing everything into one product story
  • start hardening reusable F# guidance and learned seams so future agents and humans can recover them without rediscovery

Current Truths

  • NEXUS-EMERGING is the foundation workspace, not the final extracted app repo
  • raw acquisition, canonical history, and derived projections are treated as distinct layers
  • LOGOS is the knowledge and historical substrate direction
  • CORTEX is the AI and agent-coordination direction
  • FORGE is the direction for turning repeated useful work into deterministic, reviewable surfaces
  • canonical history should remain append-only and corrections should be additive
  • durable docs are preferred over chat-only memory for anything that will matter later

Open Questions

  • what the final graph ontology should be
  • where the long-term Event Modeling tool should live between NEXUS, FnTools, and app-line repos
  • how much live capture and interaction should stay in the foundation repo versus extracted downstream repos
  • what the right next split points are for doctrine versus reusable tooling versus concrete app lines

Next Likely Actions

  • keep making shared agent memory surfaces explicit
  • keep the ingestion and canonical-history direction traceable
  • support extracted repos such as CheddarBooks with local memory surfaces while retaining upstream doctrine here
  • move repeated AI-assisted workflows toward more deterministic surfaces where practical
  • keep building a reusable F# knowledgebase that can later be reworked into stronger onboarding and training material