01 · Policy-to-code compliance mapper
Trace requirements to specific controls, tests, evidence owners and exceptions, with jurisdiction and effective-date versioning.
RESEARCH & KNOWLEDGE / PROJECTS & ARCHITECTURE
Working framework published 13 November 2026. A connected programme for studying software and AI architectures, comparing original source code with authorised educational derivatives, assessing legal and regulatory duties, testing cybersecurity and safeguarding controls, and documenting measurable outcomes. It supports academic research, professional learning, reproducible engineering and independent scrutiny. The project pathways below are proposals and reusable specifications unless explicitly linked to an implemented repository and tested result.
Existing project register · Research programme · Research questions · Dated change record.
| Evidence layer | Minimum required record | Why it matters |
|---|---|---|
| 1. Published foundation | Original paper, publication year, version, DOI or permanent URL, claims, limitations and related work | Prevents undocumented borrowing and separates established findings from proposed contributions. |
| 2. Upstream code and provenance | Official repository, immutable commit SHA or release, licence, copyright notices, dependencies, known issues, archived reference | Establishes exactly which artefact was inspected or reused; public visibility does not automatically grant reuse rights. |
| 3. Study and reconstruction | Architecture diagram, annotated modules, data flows, threat model, design decisions, synthetic fixtures, permitted fork or clean-room implementation | Makes system mechanisms understandable without implying access to private code or confidential systems. |
| 4. Three learning pathways | Beginner worked example; intermediate modular adaptation; advanced cross-system evaluation; separate branches or clearly versioned folders | Permits accessible entry without sacrificing advanced research or architecture detail. |
| 5. CI/CD and release assurance | Test plan, peer review, dependency and secret checks, SBOM where appropriate, build provenance, deployment hash, approvals, rollback | Links claimed controls and intended features to verified artefacts and releases. |
| 6. Operational outcomes | Accessibility, accuracy, security, reliability, privacy, fairness, incident and performance indicators with dated baselines | Distinguishes implementation from evidence of success, failure or inconclusive findings. |
| 7. Publication and continuity | Paper type, research question, methodology, results, counter-evidence, limitations, data/code availability, contributor attribution, revision and correction log | Supports reproducibility, professional review and long-term evidence preservation. |
Both arrangements are supported: one project repository with beginner/, intermediate/ and advanced/ directories, or three separately versioned code repositories where licensing, deployment, ownership or independent releases justify separation. In either approach, all levels should link back to the same source paper, upstream version and project identifier.
| Pathway | Example scope | Evidence/acceptance gate |
|---|---|---|
| Beginner | Read the architecture, trace a request, run a minimal local example with synthetic data, annotate a small component, explain trust boundaries and licensing. | Reproducible setup, understandable diagram, basic validation tests, accessible README and no exposed secrets. |
| Intermediate | Modular redesign, automated tests, least-privilege configuration, dependency inventory, CI, error handling, accessibility and privacy review. | Repeatable test suite, documented change comparison, dependency review, explicit acceptance criteria and release notes. |
| Advanced | Multiple services or agents, provenance-aware evaluation, independent assurance, resilience and counterfactual comparisons, authorised deployment telemetry. | Threat-model and risk review, independent replication, baseline versus deployment results, governance evidence and incident/rollback plan. |
Suggested skeleton: README.md, LICENSE, CITATION.cff, sources/upstream.md, papers/, docs/architecture.md, docs/compliance-matrix.md, docs/threat-model.md, beginner/, intermediate/, advanced/, tests/, evidence/, .github/workflows/, CHANGELOG.md and SECURITY.md. Actual files are created when an individual project starts; this is a reference structure, not a claim they already exist.
Existing Manifold Grace repository · GitHub repository duplication guidance · Template repository guidance.
Use the subject filter to explore candidate projects. Each family can support three difficulty levels and multiple distinct paper forms; no example is presented as a completed build. Additional interdisciplinary candidate families (16–23) appear below.
Trace requirements to specific controls, tests, evidence owners and exceptions, with jurisdiction and effective-date versioning.
Trace source releases, components, dependency manifests, attestations and intended versus deployed artefacts.
Study authenticated application architecture, input validation, access control and safe logging using non-sensitive synthetic examples.
Model personal-data collection, minimisation, retention, purpose limits, subject access, deletion requests and audit trails.
Compare model versions against labelled, consent-aware test sets; log uncertainty, failures, human decisions and corrections.
Study tools, delegated permissions, approvals, policy checks, provenance and safe exception handling across agents.
Preserve original source dates, revisions, stable links and evidence comparisons across publishers and decades.
Test how a digital service handles alternative formats, reasonable adjustments, human review and administrative corrections.
Evaluate detection records, escalation, containment governance, backup verification, incident notices and recovery outcomes in a controlled simulation.
Compare contract requirements, suppliers, licensing, geographic data custody, security evidence and exit strategies.
Trace dataset origin, transformations, permissions and downstream model or decision outputs with independently testable evidence links.
Compare documented authority, procedural decisions, independent oversight, correction handling and public-interest reporting.
Compare approved build/configuration, pre-release tests and observed production behaviour using authorised read-only monitors.
Evaluate protective workflows, reporting routes, escalation safeguards, privacy controls and accessible support across service users.
Test how corrected evidence transfers between systems without flattening uncertainty, losing original dates or exposing private records.
Publication type should be selected to fit the question and evidence, not the other way around. Multiple outputs may share a project, provided their contributions and source records are distinguishable. These are potential formats, not claims that publication has occurred.
| Paper or output type | Most useful when | Required distinctions |
|---|---|---|
| Literature review / systematic or scoping review | Mapping established research, contradictions, gaps and breadth | Search dates, inclusion criteria and systematic status documented accurately. |
| Conceptual / theory paper | Defining a framework, mechanism, taxonomy or falsifiable proposition | Separate conceptual contribution from empirical validation. |
| Architecture / design-science paper | Explaining system components, design requirements, interfaces and trade-offs | Working artefact, proposed architecture and tested system clearly distinguished. |
| Methods / measurement paper | Introducing an evaluation protocol, rubric, dataset or measurement instrument | Validity, reliability, error analysis and replicability addressed. |
| Empirical experimental paper | Testing causal or performance hypotheses with controlled comparisons | Predefined variables, baselines, limitations and negative findings. |
| Replication / reproducibility study | Testing whether a published result or code artefact can be reproduced | Original experimental conditions and deviations reported. |
| Comparative benchmark paper | Contrasting models, architectures, controls or versions | Fair datasets, environments, baselines and uncertainty. |
| Software / research artefact paper | Presenting a reusable, documented implementation | Release, licence, dependencies, tests and citation details. |
| Security / assurance evaluation | Evaluating authorised defensive controls and risk reduction | Defined authorisation, safe scope, evidence and responsible reporting. |
| Legal doctrinal / regulatory analysis | Interpreting duties and comparing rules across jurisdictions | Original instrument dates, applicable law and expert validation. |
| Policy / governance analysis | Comparing alternative oversight, accountability or compliance designs | Explicit normative assumptions and implementation trade-offs. |
| Case study / longitudinal study | Understanding a bounded system or changes over time | Source provenance, case selection, chronology and competing explanations. |
| Ethnographic / qualitative study | Understanding user, worker or institutional experiences | Consent, safeguarding, sampling, positionality and confidentiality. |
| Participatory / action research | Co-developing and assessing a real intervention | Participation, feedback, governance and staged evaluation. |
| Position / perspective / commentary | Arguing for a research direction or questioning accepted assumptions | Argument and proposed validation distinguished from established results. |
| Registered report / preregistered protocol | Publishing proposed questions, design and analysis before results | Preregistration does not imply completed experiments or journal acceptance. |
| Technical report / audit and assurance report | Documenting professional testing, findings and corrective recommendations | Scope, criteria, access, evidence status and reviewer limitations. |
| Education / curriculum or practitioner guide | Teaching architecture with segmented worked examples | Original-source attribution, learning objectives and safe exercises. |
Project ID; concept and context; audience and intended use; project owner and responsible reviewers; current maturity (concept / design / prototype / tested / deployed); architecture and data-flow diagrams; upstream paper and repository/release/commit; licences and attribution; downstream derivation and code-diff record; beginner, intermediate and advanced learning objectives; relevant legal jurisdictions; compliance requirements; threat model and safeguards; privacy and ethical approval; test baselines; CI/CD evidence; expected and observed outcomes; limitations, counter-evidence and incidents; accessibility; stakeholder feedback; maintainers; dependencies and funding; reproducibility; release and review dates; correction and deprecation policy.
Conceptual idea: problem, prior work, context and proposed contribution. Research project: objectives, ownership, work packages, milestones and resources. Paper initiative: prospective paper type, working outline, evidence needs and publication status. Contextual research question: scope, variables, counter-hypotheses and falsification plan. Productivity log: dated action, verified evidence link, why it matters and next step. Link all five by stable project ID. Create them as actual records when a specific project begins; do not label a proposal as a completed paper.
Intake and relevance → upstream licence and citation verification → architecture review → privacy, safeguarding and regulatory assessment → threat model → implementation and peer review → synthetic-data testing → CI/CD checks → authorised deployment → post-deployment evaluation → independent replication → release, incident correction and retirement. Different risks warrant different levels of oversight; legal interpretation should be reviewed by a qualified specialist where needed.
Every implemented level should have a measured baseline, testable functional requirements, security and accessibility checks, evidence of approved deployment, date-stamped results, known failure cases and a reviewer-visible change log. A passing test is not proof of legal compliance or absence of vulnerabilities. Compare like-for-like versions and retain negative results.
Prefer documented open-source licences or the original author's explicit permission. Preserve attribution, notices, licence compatibility and dependency obligations; do not assume public repositories are licensed for cloning or modification. Never bypass authentication or paywalls, retrieve private code without authority, collect sensitive data without suitable safeguards, or test third-party systems without permission.
Source publication or release dates are preserved here rather than substituted with the date of this framework. Standards must be checked for revisions and jurisdictional applicability before using them as compliance criteria.
| Original date / version | Authoritative reference | Use in project evaluation |
|---|---|---|
| 3 February 2022 (final v1.1) | NIST SP 800-218 Secure Software Development Framework | Secure development and supply-chain practices. |
| 26 July 2024 (final) | NIST SP 800-218A — generative AI community profile | Model-specific secure development practices. |
| 17 December 2025 (initial public draft) | NIST SP 800-218 Rev. 1 draft (v1.2) | Possible future revisions, explicitly not presented as final. |
| 2021 (FAIR4RS principles; publication record) | FAIR Principles for Research Software | Findability, accessibility, interoperability and reuse. |
| Version 5.0 (see release history) | OWASP Application Security Verification Standard | Web application security requirements and tests. |
| 2024 conference guidance | ACM PADS artefact evaluation | Reproducibility, transparent experimental artefacts and review. |
| Current documentation (date varies) | GitHub artifact attestation documentation | Linking release artefacts with verifiable provenance. |
| Current documentation (date varies) | W3C accessibility standards | Accessibility acceptance criteria and inclusive design. |
Publication and verification status: this page is a design and research planning resource. Individual projects, code forks, compliance attestations, published papers and completed evaluations must be independently linked and verified before they are reported as delivered.