Skip to content
JKhyroPublic

About

Native C-first character construction and ARA management surface for the SYNAPSE suite, with Avalonia and C# only where necessary.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

36 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CORTEX

CORTEX is the canonical character-construction and character-management surface in the SYNAPSE suite.

A CORTEX character is a singular operational entity formed from an Adaptive Response Array (ARA) of bound agent components. First-class doctrine support starts with two-component and three-component ARAs, while larger arrays remain allowed where the character model justifies them.

Core ownership

  • character creation and character management interfaces
  • ARA composition, component roles, and ownership rules
  • lifecycle state, control actions, and component governance
  • per-component subagent governance, with each component able to spawn or despawn up to 12 subagents
  • the managed contracts that bind PRISM personality inputs and ASCENT progression inputs into a governed character

Cross-project contracts

  • PRISM -> CORTEX: personality matrix, overlays, stylization, and character-governance inputs
  • ASCENT -> CORTEX: achievement points, progression, reward, penalty, and state inputs
  • CORTEX -> VECTOR: managed characters and components exposed for workspace execution
  • SYMBIOSIS -> CORTEX: extracted OpenClaw, Lobster, and Hermes functionality that defines the character itself

Runtime base: Hermes-derived FURYOKU

The live agent runtime that executes CORTEX-managed characters and their ARA components has moved from OpenClaw to Hermes Agent. Hermes-derived FURYOKU is the runtime spine for the 7-Symbiote swarm; OpenClaw is demoted to a feature-harvest lane — selectively mined for character-defining functionality per the SYMBIOSIS -> CORTEX contract above, but not promoted to host. CORTEX's ARA doctrine and subagent governance rules are unchanged by the move; only the runtime that hosts the character is different. Anchor is universalized across JKhyro Project #20 (FURYOKU) and Project #10 (SYMBIOSIS).

Implementation direction

  • Native C is the primary implementation language for the CORTEX core.
  • C++ is acceptable where it materially improves the native runtime or tooling.
  • Avalonia is the preferred desktop shell where a managed UI surface is required.
  • C# is used only where Avalonia, interop hosting, or platform packaging makes it necessary.
  • Canonical behavior stays in native code behind an explicit, stable C ABI.

Architecture rule

The native core owns character modeling, ARA behavior, lifecycle control, subagent governance, and creation-management logic. Avalonia and C# remain thin host layers rather than a second runtime authority.

See docs/character-ara-doctrine.md for the character model and docs/native-c-avalonia-direction.md for the stack rule and packaging implications.

Native runtime slices

The first native C runtime slices are the imported catalog mapper for CORTEX #19 and the character/ARA lifecycle core for CORTEX #21.

cmake -S . -B "$env:LOCALAPPDATA\CORTEX\runtime-build"
cmake --build "$env:LOCALAPPDATA\CORTEX\runtime-build" --config Debug
ctest --test-dir "$env:LOCALAPPDATA\CORTEX\runtime-build" -C Debug --output-on-failure

The current native entry points are include/cortex/imported_catalog_mapper.h and include/cortex/character_runtime.h. They expose the mapper ABI, character/runtime ABI, lifecycle state/actions, stable outcome/error enums, governed imported-helper binding, and subagent capacity guards.

Current specification set

Current execution status

  • CORTEX #3: Done
  • CORTEX #9: Done
  • CORTEX #19: Done
  • CORTEX #21: Done
  • CORTEX #24: Done
  • CORTEX #27: Active (native host surface for persisted runtime workflows)
  • CORTEX #2: Done

Functional readiness

CORTEX is roughly 38% complete toward a usable runnable product. The contract set, static progress prototype, native imported catalog mapper, native character/ARA lifecycle core, and first durable runtime persistence slice are in place with executable tests. The active lane is the first native operator host over those persisted workflows; shell integration, real external catalog feed wiring, and installable packaging still remain.

About

Native C-first character construction and ARA management surface for the SYNAPSE suite, with Avalonia and C# only where necessary.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages