Showcases

The reqlan development patterns are appropriate to model many types of systems. This page showcases some domains and problems that reqlan is particularly well-suited for. If you have a project that you'd like us to feature here, please reach out to us.

MCP + token disciplineflagship

aimcpplanning

Context for the agent, not the repo

Six ideas and their edges beat forty files. Hand the agent a shaped slice.

symbol · line · test anchorsflagship

industrialsafetysequencing

The interlock that must not fail

A safety requirement bound to ST by line range, to a test by name, and back by an rq: comment.

diagnostics + check + CIflagship

diagnosticsrefactorclici

Links that break loudly

Rename a file. Editor diagnostic, rewritten refs, then `reqlan check` in CI. Not a wiki.

cross-stack file refsflagship

integrationcross-stackembedded

Firmware meets the cloud

10 Hz on the device, 50 ms on the ingest path - one invariant neither codebase can hold alone.

story ↔ source ↔ testsflagship

storytraceabilitydelivery

The story that ships with the code

Write the feature in .rq. @implementation and @tests name the files. rq: comments point back.

attributes · completion · HTML export

complianceauditexport

An audit trail you can export

Custom clause attributes, a coverage gap from Completion Status, HTML export for the auditor.

ideasets as public API

modularityimportsideasets

A module's published surface

billing exports an ideaset. checkout imports only that. Reaching past the boundary is an error.

test-name anchors

testingtraceability

What this test actually proves

Test-name anchors bind intent to the case. The test file points back.

comment links · deprecation impact

legacydiscoverydeprecation

Archaeology on inherited code

Seed an rq: comment into an undocumented function, mark the old path @deprecated, see impact.

Cytoscape · filters · depth

extensiongraph

See the whole graph

Cytoscape in Ideas Summary - filter by status or tag, toggle indirect depth.

full attribute grammar

attributesextensibility

Attributes as a domain dialect

Flags, negated flags, block values, nested lists - arbitrary @keys without changing the grammar.

pointers, not data

antipatterncraft

Three ways to write .rq badly

Data instead of pointers, prose restating code, one monolithic file. Negative space is taste.