JSON config validation
Load, parse, and structurally validate JSON configuration files against declared schema expectations. Reject malformed input before any downstream processing.
Roadmap
Where Aeostara is headed as a Raven Forge Software project — from deterministic repair to continuous self-healing across platforms, formats, and operational environments.
Current scope
A complete deterministic self-healing pipeline for JSON configuration files on Windows.
Load, parse, and structurally validate JSON configuration files against declared schema expectations. Reject malformed input before any downstream processing.
Compare actual configuration state against the declared desired state. Identify additions, removals, and value changes with precise key-path reporting.
Evaluate repair decisions against declared policy invariants. Only actions that satisfy constraints proceed. Policy violations halt execution before mutation.
Generate and execute repair plans from explicit rules. Same drift always produces same correction. Backup, apply, verify, and rollback on every operation.
Every detection, evaluation, repair, and rollback is recorded in an append-only JSON Lines log. Complete operational history for compliance and debugging.
Three core commands — validate, diff, and heal — provide direct access to the full self-healing lifecycle from the command line. Transparent, scriptable, composable.
Next steps
The capabilities being developed for subsequent releases.
The core healing engine moves from inline logic to a standalone pattern-matching kernel. ASH becomes a discrete, testable layer responsible for all detection-to-repair computation — separated from platform adapters and CLI tooling.
Richer policy evaluation with compound constraints, conditional rules, and scoped invariants. Policies gain the ability to express dependencies between properties, threshold-based triggers, and environment-specific overrides.
Extend configuration handling beyond JSON to include YAML and TOML. Each format receives its own parser and serializer, while sharing the same drift detection, policy evaluation, and repair pipeline.
Real-time watch mode that monitors configuration files for changes and triggers the detection-repair loop automatically. File system events drive the healing cycle without polling overhead.
Long term
Aeostara is designed as a cross-platform project from the beginning. The Windows implementation is developed first in C++20, followed by native macOS and iOS implementations in Swift. Each platform receives a native build — not a cross-compiled port — tailored to the conventions and toolchains of its environment.
Planned enterprise features include centralized policy management, fleet-wide configuration enforcement, role-based access control for repair authorization, and integration with existing compliance and audit infrastructure. Designed for teams that manage configuration at scale.
A programmatic API layer will expose the full self-healing lifecycle for integration into CI/CD pipelines, deployment orchestrators, and custom tooling. Every operation available through the CLI will be available through a structured API with typed contracts.