TENIR Labs · Portfolio
REG-ARCH
On this page
Framework and research
Requirements, actions and evidence: how do they connect?
Requirements, actions and evidence evolve separately. Their links, responsibilities and conditions for moving between states become difficult to follow.
- What you receive
- Conceptual map and typed transition model to compare with versioned source specifications.
Explanation or demonstration on this site.
AVAILABLE RESOURCEView interactive architecture
Open resource ↗Illustrative diagram
See whether it fits your situation
- This may help when…
- When architects need to connect claims, actions and their representation across Claim, Action and Representation.
- What you need to start
- Requirements, action/effect states, representation artifacts, responsibilities and assumptions.
- What is examined
- Objects, transitions, gates and bindings across Claim / Action / Representation lanes.
- The starting question
- Requirements, actions and evidence evolve separately. Their links, responsibilities and conditions for moving between states become difficult to follow.
- How it connects to other approaches
- Connects Prevent, Prepare, TENIR-Gov and explanatory experiences; not an additional client offer.
- Availability and maturity
- REG-ARCH v0.4 referenced in project artifacts; authoritative public version and ratification not verified.
- Limits to keep in mind
- An architecture diagram is not an implementation, a successful test or an adopted standard.
- A possible next step
- Inspect illustrative architecture, then verify the appropriate versioned specification with a qualified owner.
Read sources and version references
Availability and limits above reflect the cited sources. Unverified artifact revisions remain identified.