Retrace README

Project documentation for the Retrace ecosystem.

Retrace Enterprises is the public gateway for web projects, desktop software, security utilities, and narrative technical systems.

View Project Map Back to Gateway

Project Map

The ecosystem is split into distinct branches so each product surface keeps its own language and release rhythm.

Gateway

Retrace Enterprises

Main public landing surface for branch navigation, tools, privacy, standards, and product routing.

Classic Desktop

Keyform Software

VB6-style desktop software with local-first utilities, release notes, downloads, and support documentation.

Modern Systems

Synantix Systems

Experimental systems and technical instrumentation branch for dense interfaces, analysis concepts, and product docs.

Modern Desktop

Nova Labs

Modern desktop software branch for efficient tools around files, storage, search, logs, and everyday data work.

Products

SPECDRIS & VANTH

Synantix product surfaces for adaptive threat mapping, command intelligence, cognitive analysis, and probabilistic inference.

Technical Profile

The public build favors inspectable dynamic surfaces, with legacy and tooling assets preserved where they still belong.

Core Stack

  • HTML, CSS, and JavaScript for current public frontend pages.
  • PHP utilities and older standalone functionality remain active in the wider environment.
  • Static product documentation with embedded examples and structured data.

Documentation Surface

  • JSON examples and JSON Schema examples for detailed docs.
  • Docker Compose examples where deployment concepts are part of the product or technical surface.
  • Public copy keeps prototype and production language separate.
Operating Principles

Keep the system legible.

1
Clear branches Retrace is the gateway, Synantix is the experimental systems branch, Keyform is the classic desktop software branch, and Nova Labs is the modern desktop tools branch.
2
Honest release language Prototype documentation should not be presented as a guaranteed production service without a matching implementation and release channel.
3
Defensive framing Security-oriented material should stay clearly defensive, educational, or analytical.
4
Transparent behavior Public pages should be clear about privacy, downloads, and expected behavior.

Documentation should feel like part of the gateway, not an afterthought.

Return Home