Capabilities

A technical surface that can grow with the project.

Blue Lizard is being shaped around a shared backend model, with the CLI and MCP interface as practical entry points. The status beside each capability is intentionally conservative.

Feature map

Intended capabilities, described precisely.

Blueprint-based backend representation

Describe backend structure as a shared model of services, operations, and relationships. This addresses the gap between scattered source files and the system those files form.

In progressThe blueprint direction is part of the active project scope; exact syntax and persistence are evolving.

Typed nodes and connections

Make important backend relationships explicit, so tools can reason about valid connections and the operations that pass between them.

PlannedThe concept is defined at the product level; a verified public implementation is not available in this repository.

Intermediate representation and validation

Create a validation boundary between a project description and later build steps, with room for structural and configuration checks.

PlannedValidation is a planned capability; no implementation claim is made here.

Backend build orchestration

Coordinate the processing required to turn a structured backend project into a buildable application target.

In progressThe CLI-oriented build workflow is part of the evolving direction; supported targets are not yet documented as stable.

CLI workflows

Give developers a direct command-line surface for working with Blue Lizard projects.

In progressThe package name and executable are defined for the project, but publication and current command behavior require verification.

MCP integration

Offer structured tools to compatible AI coding agents through a Model Context Protocol interface.

PlannedThe integration is described as intended; no installation command is presented without verified implementation.

Security-oriented checks

Help surface unsafe patterns, configuration issues, and authorization concerns earlier in the development workflow.

PlannedSecurity analysis is a planned direction, not a security guarantee or a completed scanner.

Runtime and serving workflows

Provide a consistent way to start supported backend applications after the project has been processed.

PlannedServing is part of the intended workflow; supported runtimes are not yet verified here.

Diagnostics and error reporting

Return actionable context about configuration, build failures, and potential security problems.

PlannedDiagnostics are a design goal; the exact error format remains subject to change.

Future extensibility

Keep the shared model open to additional backends, checks, integrations, and developer workflows over time.

PlannedExtensibility is a long-term principle rather than a claim about a current plugin system.

Track the implementation as it evolves.

The roadmap separates the foundation work from longer-term capabilities and only marks verified items as available.

Open development roadmap