Nastavia Delivers First NaviMArc-Based ToR
Nastavia has successfully delivered its first complex Terms of Reference covering both Stakeholder Requirements Specification (StRS) and System Requirements Specification (SyRS) levels using NaviMArc, the Nastavia Machine-Actionable Architecture. The engagement provided an opportunity to apply NaviMArc in a real, multi-stakeholder business environment where requirements had to remain traceable, structured and technically actionable while still being practical for business owners, subject-matter experts and multiple RACI roles to review and approve.
This practical business interaction is also what distinguishes NaviMArc from many emerging Spec-Driven Development approaches. Modern SDD increasingly treats specifications as the primary source from which technical plans, tasks and implementations can be generated, but many current approaches still rely heavily on structured Markdown, natural-language templates and AI interpretation. GitHub Spec Kit, for example, explicitly follows a specification-to-plan-to-tasks-to-implementation workflow and produces Markdown artifacts for AI coding agents. NaviMArc approaches the problem from another direction: its XML representation provides a controlled, machine-actionable semantic backbone, while business users are not expected to work with that representation directly.
Instead, NaviMArc is designed around bidirectional projection between the canonical specification and familiar collaborative tools such as Microsoft Excel and Google Sheets. For the business user, requirements remain ordinary tables that can be filtered, reviewed, edited and commented on without introducing another specialist application or notation. Behind that familiar interface, NaviMArc preserves object identity, classification, hierarchy, relationships and traceability. Changes can therefore move in both directions: structured specification data can be rendered into business-friendly working views, while controlled changes made in those views can be synchronized back into the canonical model. Narrative content is handled alongside structured data through embedded Markdown blocks, allowing context, rationale and explanatory material to remain part of the same specification architecture without forcing everything into tabular form.
The successful delivery demonstrates the central NaviMArc principle: machine-actionable specifications do not require business stakeholders to become users of a formal specification language. The formal structure can remain underneath, while people continue working in the tools and representations they already understand. This creates a practical bridge between business analysis, formalized requirements, collaborative review and emerging AI-assisted development practices, while keeping the specification itself as the persistent source of truth rather than reducing it to a document produced only for handover.
