Kevin Cervantes · About Us

Software and AI systems built around legible state.

I build software and AI systems spanning governed agents, personal context tools, simulation, visual computing, and practical desktop software. MiDex is the flagship live product; the other work below is labeled by its actual publication and development state.

Selected systems

Featured work

Each card separates the motivation, present implementation state, and public boundary.

Live product · private source

MiDex

LIVE

A conversation-first personal context system where durable Memory remains reviewable and user-controlled.

Why it exists: Useful continuity should not require people to administer a second system or surrender control over what lasts.
Where it is now: The public Conversation surface is live. Source, production diagnostics, and user context remain private.

Transient Conversation and reviewed Memory remain distinct
Retention and provider authority are visible product boundaries
Public positioning is tested alongside application behavior

Use MiDex

Public V1 · advanced work private

Omega

ACTIVE DEVELOPMENT

A governed Civilization VI agent that constrains model choices to current candidates, executes through deterministic workers, and verifies what changed.

Why it exists: A strategy game provides a concrete place to separate model judgment from authority, execution, and evidence.
Where it is now: The public implementation demonstrates the core coordinator and worker boundary. Broader continuity and strategic evaluation remain qualified development work.

Structured observation and legal-action selection
Deterministic execution with post-action verification
Replayable evidence and explicit failure states

View Omega on GitHub

Documentation candidate · private source

Astrolabe

ACTIVE DEVELOPMENT

A local-first execution-governance framework designed to keep agent intent, authority, execution, evidence, and acceptance as separate boundaries.

Why it exists: Automation is easier to trust when planning, permission, execution, and independent acceptance cannot silently collapse into one step.
Where it is now: Several bounded pilot slices are qualified. Repository canonicalization and broader integration remain active work, so no public implementation is linked yet.

Signed grants and receipts
Disposable, bounded execution fixtures
Independent evidence acceptance

No public implementation link is asserted.

Additional work

Public links appear only where a current public surface exists.

Frozen public research release

Parallax

FROZEN PUBLIC RELEASE

A governed evaluation project for stress-testing strategic AI advice without treating plausible answers as ground truth.

Why it exists: Negative results and evidence limits should survive publication instead of being polished away.
Where it is now: The linked release is frozen and its microsite remains public. Its public package—not later local development state—is the authority for portfolio claims.

Preregistered evaluation
Append-only evidence
Reproducible release boundary

View the frozen public release Open the Parallax microsite

Original successor · private source

Requiem

ACTIVE DEVELOPMENT

An original deterministic defense-game successor developed with a strict boundary from a private preservation and compatibility-research corpus.

Why it exists: Deterministic simulation and replay make game behavior inspectable across runtime and presentation layers.
Where it is now: The original successor is in active development. Archaeology material and related evidence are deliberately withheld.

Deterministic Python kernel
Godot presentation
Cross-runtime replay conformance

No public implementation link is asserted.

Technical case study · private source

Helios

TECHNICAL DEMONSTRATOR

Native Android and OpenGL ES work on procedural solar visuals, numerical stability, and device-aware rendering.

Why it exists: Visually rich simulation has to remain stable under real device, precision, lifecycle, and thermal constraints.
Where it is now: Substantial bounded technical work exists, but production completion and broad device compatibility are not claimed.

WallpaperService lifecycle
OpenGL rendering
Device-bounded numerical qualification

No public implementation link is asserted.

Public MIT implementation

ScreenComfort

PUBLIC

A Windows utility for scheduled hardware brightness and software gamma control, with an installer and recoverable local runtime.

Why it exists: Display comfort should be automatable without hiding the difference between monitor hardware support and software fallback.
Where it is now: The public repository contains the current implementation. Hardware behavior still depends on monitor DDC/CI support.

DDC/CI brightness
Gamma fallback
Task Scheduler integration

View ScreenComfort on GitHub

Reading the work

Status is part of the claim.

“Private” means deliberately withheld, not absent. It does not imply public availability, production readiness, or broader capability than the card states.

LIVE: The product is publicly available now; source may still remain private.
ACTIVE DEVELOPMENT: Meaningful implementation exists, while completion and capability remain bounded.
FROZEN PUBLIC RELEASE: The linked public artifact is deliberately version-bound and preserved.
TECHNICAL DEMONSTRATOR: A functioning technical exploration, not a generally complete product.
PUBLIC: A current public implementation can be inspected under its stated license.

MiDex

Loading MiDex

The requested view is loading. Existing state remains intact while this completes.

Kevin Cervantes · About Us

Software and AI systems built around legible state.

Selected systems

Featured work

Each card separates the motivation, present implementation state, and public boundary.

Live product · private source

MiDex

LIVE

A conversation-first personal context system where durable Memory remains reviewable and user-controlled.

Why it exists: Useful continuity should not require people to administer a second system or surrender control over what lasts.
Where it is now: The public Conversation surface is live. Source, production diagnostics, and user context remain private.

Transient Conversation and reviewed Memory remain distinct
Retention and provider authority are visible product boundaries
Public positioning is tested alongside application behavior

Use MiDex

Public V1 · advanced work private

Omega

ACTIVE DEVELOPMENT

A governed Civilization VI agent that constrains model choices to current candidates, executes through deterministic workers, and verifies what changed.

Why it exists: A strategy game provides a concrete place to separate model judgment from authority, execution, and evidence.
Where it is now: The public implementation demonstrates the core coordinator and worker boundary. Broader continuity and strategic evaluation remain qualified development work.

Structured observation and legal-action selection
Deterministic execution with post-action verification
Replayable evidence and explicit failure states

View Omega on GitHub

Documentation candidate · private source

Astrolabe

ACTIVE DEVELOPMENT

A local-first execution-governance framework designed to keep agent intent, authority, execution, evidence, and acceptance as separate boundaries.

Why it exists: Automation is easier to trust when planning, permission, execution, and independent acceptance cannot silently collapse into one step.
Where it is now: Several bounded pilot slices are qualified. Repository canonicalization and broader integration remain active work, so no public implementation is linked yet.

Signed grants and receipts
Disposable, bounded execution fixtures
Independent evidence acceptance

No public implementation link is asserted.

Additional work

Public links appear only where a current public surface exists.

Frozen public research release

Parallax

FROZEN PUBLIC RELEASE

A governed evaluation project for stress-testing strategic AI advice without treating plausible answers as ground truth.

Why it exists: Negative results and evidence limits should survive publication instead of being polished away.
Where it is now: The linked release is frozen and its microsite remains public. Its public package—not later local development state—is the authority for portfolio claims.

Preregistered evaluation
Append-only evidence
Reproducible release boundary

View the frozen public release Open the Parallax microsite

Original successor · private source

Requiem

ACTIVE DEVELOPMENT

An original deterministic defense-game successor developed with a strict boundary from a private preservation and compatibility-research corpus.

Why it exists: Deterministic simulation and replay make game behavior inspectable across runtime and presentation layers.
Where it is now: The original successor is in active development. Archaeology material and related evidence are deliberately withheld.

Deterministic Python kernel
Godot presentation
Cross-runtime replay conformance

No public implementation link is asserted.

Technical case study · private source

Helios

TECHNICAL DEMONSTRATOR

Native Android and OpenGL ES work on procedural solar visuals, numerical stability, and device-aware rendering.

Why it exists: Visually rich simulation has to remain stable under real device, precision, lifecycle, and thermal constraints.
Where it is now: Substantial bounded technical work exists, but production completion and broad device compatibility are not claimed.

WallpaperService lifecycle
OpenGL rendering
Device-bounded numerical qualification

No public implementation link is asserted.

Public MIT implementation

ScreenComfort

PUBLIC

A Windows utility for scheduled hardware brightness and software gamma control, with an installer and recoverable local runtime.

Why it exists: Display comfort should be automatable without hiding the difference between monitor hardware support and software fallback.
Where it is now: The public repository contains the current implementation. Hardware behavior still depends on monitor DDC/CI support.

DDC/CI brightness
Gamma fallback
Task Scheduler integration

View ScreenComfort on GitHub

Reading the work

Status is part of the claim.

“Private” means deliberately withheld, not absent. It does not imply public availability, production readiness, or broader capability than the card states.

LIVE: The product is publicly available now; source may still remain private.
ACTIVE DEVELOPMENT: Meaningful implementation exists, while completion and capability remain bounded.
FROZEN PUBLIC RELEASE: The linked public artifact is deliberately version-bound and preserved.
TECHNICAL DEMONSTRATOR: A functioning technical exploration, not a generally complete product.
PUBLIC: A current public implementation can be inspected under its stated license.