Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,6 +206,9 @@ Mintlify docs live in [`docs/mintlify`](docs/mintlify):
- [Builder & Validator Sandbox](docs/mintlify/getting-started/builder-validator-sandbox.mdx)
- [AI SDLC Trends & Loopholes](docs/mintlify/reference/loopholes-roadmap.mdx)
- [Business Hub](docs/mintlify/reference/business-hub.mdx)
- [Research Program](docs/mintlify/reference/research-program.mdx)

Research-paper source material lives in [`research/`](research/): bibliography, methodology, prior-art comparison, productivity claims discipline, design history, paper outline, and the current-state audit.

The original presentation is kept as a backup at:

Expand Down
6 changes: 4 additions & 2 deletions docs/mintlify/docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,8 @@
"reference/business-hub",
"reference/approvals",
"reference/webhooks",
"reference/loopholes-roadmap"
"reference/loopholes-roadmap",
"reference/research-program"
]
},
{
Expand Down Expand Up @@ -88,7 +89,8 @@
"reference/observability",
"reference/configuration",
"reference/protected-actions",
"reference/loopholes-roadmap"
"reference/loopholes-roadmap",
"reference/research-program"
]
}
]
Expand Down
3 changes: 2 additions & 1 deletion docs/mintlify/mint.json
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,8 @@
"reference/pi-tools",
"reference/observability",
"reference/configuration",
"reference/protected-actions"
"reference/protected-actions",
"reference/research-program"
]
}
],
Expand Down
70 changes: 70 additions & 0 deletions docs/mintlify/reference/research-program.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
---
title: "Research Program"
description: "Bibliography, methodology, claims discipline, and prior-art comparison for the RStack SDLC research paper."
---

RStack is being developed as both a product and a research-backed AI-SDLC operating model. This page links the research artifacts that explain what RStack implements today, what it claims, what remains a hypothesis, and how future productivity claims should be measured.

## Research thesis

RStack improves the practical use of AI coding agents by wrapping them in a governed lifecycle:

```text
clarify → plan → spec → approve → build → validate → release-readiness → learn
```

The careful version of the thesis is:

> RStack does not claim that AI coding alone guarantees productivity. RStack claims that AI-assisted delivery becomes more reliable and measurable when work is constrained by lifecycle stages, approvals, typed handoffs, evidence, budget envelopes, and Business Hub observability.

## Repo research artifacts

| Artifact | Purpose |
|---|---|
| [`research/current-state-audit.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/current-state-audit.md) | Detailed audit of where RStack stood before the research roadmap implementation. |
| [`research/bibliography.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/bibliography.md) | Standards, prior art, empirical research, and RStack primary-source references. |
| [`research/methodology.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/methodology.md) | How to study RStack and what metrics to collect. |
| [`research/prior-art-ai-sdlc-framework.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/prior-art-ai-sdlc-framework.md) | Comparison with `ai-sdlc-framework/ai-sdlc` and AI-SDLC reference architecture patterns. |
| [`research/productivity-claims.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/productivity-claims.md) | Claims register separating implemented facts, external evidence, hypotheses, and unsupported claims. |
| [`research/rstack-design-history.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/rstack-design-history.md) | Primary-source narrative of current implementation and design history. |
| [`research/paper-outline.md`](https://github.com/richard-devbot/SDLC-rstack/blob/main/research/paper-outline.md) | Draft paper structure and thesis. |

## Claims discipline

Every RStack paper or docs claim should have at least one of:

1. measured evidence from RStack runs, tests, PRs, or CI,
2. source evidence from standards, reports, or prior art,
3. implementation evidence from code or docs,
4. a clear hypothesis label and experiment plan.

<Warning>
Do not claim quantified productivity gains until RStack has measured comparison runs. The current research-safe claim is that RStack creates the lifecycle and evidence structure needed to measure and improve AI-assisted delivery.
</Warning>

## Research-backed roadmap

The research program is tracked in GitHub issues:

- [#70 Decision Queue and Definition-of-Ready gate](https://github.com/richard-devbot/SDLC-rstack/issues/70)
- [#71 RStack Spec v1alpha1](https://github.com/richard-devbot/SDLC-rstack/issues/71)
- [#72 Cross-harness builder/validator review independence](https://github.com/richard-devbot/SDLC-rstack/issues/72)
- [#73 RStack attestation envelopes](https://github.com/richard-devbot/SDLC-rstack/issues/73)
- [#74 Traceability drift detection](https://github.com/richard-devbot/SDLC-rstack/issues/74)
- [#75 Untrusted contributor PR gate](https://github.com/richard-devbot/SDLC-rstack/issues/75)
- [#76 RFC / Architecture Decision Record process](https://github.com/richard-devbot/SDLC-rstack/issues/76)
- [#77 Research bibliography and methodology appendix](https://github.com/richard-devbot/SDLC-rstack/issues/77)
- [#78 Governance packs and profile-based enforcement levels](https://github.com/richard-devbot/SDLC-rstack/issues/78)

## Suggested paper measurement model

RStack should measure productivity through multiple lenses:

- delivery flow: time to plan, build, validate, and release-readiness,
- quality: builder/validator pass rates, retries, risks, tests run,
- governance: approvals, blocked gates, policy overrides,
- traceability: requirement-to-task-to-evidence completeness,
- cost: estimated vs actual usage when host/provider data is available,
- operator burden: number of human interventions per run.

See `research/methodology.md` for the full measurement plan.
1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,7 @@
"plugins/",
"docs/public/",
"docs/HARNESS.md",
"research/",
"operator.json",
"README.md"
],
Expand Down
122 changes: 122 additions & 0 deletions research/bibliography.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,122 @@
<!-- owner: RStack developed by Richardson Gunde -->

# RStack Research Bibliography

This bibliography records the sources used to ground the RStack SDLC research narrative. It separates standards, prior-art implementations, empirical productivity evidence, security references, and RStack primary-source artifacts so the paper can cite claims without reconstructing context later.

## Standards and governance references

### NIST AI Risk Management Framework
- **Reference:** National Institute of Standards and Technology, *AI Risk Management Framework*.
- **URL:** https://www.nist.gov/itl/ai-risk-management-framework
- **Why it matters to RStack:** RStack's governance model can map Business Hub observability, approvals, validation contracts, and future governance packs to AI risk management practices.
- **RStack connection:** Supports roadmap issues for governance packs, RStack Spec v1alpha1, cross-harness validation, and claims discipline.

### NIST SP 800-218 Secure Software Development Framework
- **Reference:** National Institute of Standards and Technology, *SP 800-218: Secure Software Development Framework (SSDF) Version 1.1*.
- **URL:** https://csrc.nist.gov/pubs/sp/800/218/final
- **Why it matters to RStack:** SSDF states that secure software practices must be added explicitly to SDLC models. RStack's value proposition is exactly this: make approvals, evidence, validator contracts, guardrails, and release readiness explicit in AI-assisted delivery.
- **RStack connection:** Supports evidence, validator contracts, untrusted PR gates, and release-readiness checks.

### ISO/IEC 42001:2023 AI management systems
- **Reference:** International Organization for Standardization, *ISO/IEC 42001:2023 — Information technology — Artificial intelligence — Management system*.
- **URL:** https://www.iso.org/standard/81230.html
- **Why it matters to RStack:** Gives enterprise context for treating AI-assisted development as a governed management system instead of ad-hoc tooling.
- **RStack connection:** Supports profile-based governance levels, enterprise-webapp profile, research claims, and future compliance mapping.

### EU AI Act overview
- **Reference:** EU Artificial Intelligence Act tracker and analysis site.
- **URL:** https://artificialintelligenceact.eu/
- **Why it matters to RStack:** Provides regulatory motivation for traceability, transparency, risk management, and documented oversight in AI workflows.
- **RStack connection:** Supports research-paper framing around governed AI software delivery.

## Secure supply-chain and attestation references

### SLSA Provenance
- **Reference:** Supply-chain Levels for Software Artifacts, *Provenance specification*.
- **URL:** https://slsa.dev/spec/v1.0/provenance
- **Why it matters to RStack:** RStack's future attestation envelope should record where, when, and how an agent-produced artifact was created and validated.
- **RStack connection:** Supports future `rstack-agents attest` and `verify-attestations` work.

### DSSE specification
- **Reference:** Secure Systems Lab, *DSSE: Dead Simple Signing Envelope*.
- **URL:** https://github.com/secure-systems-lab/dsse
- **Why it matters to RStack:** Provides an envelope pattern for signing structured payloads. RStack can adapt this pattern for builder, validator, and release-readiness evidence.
- **RStack connection:** Supports attestation roadmap and paper claims about tamper-evident evidence.

### Sigstore documentation
- **Reference:** Sigstore documentation.
- **URL:** https://docs.sigstore.dev/
- **Why it matters to RStack:** Provides a practical signing/provenance ecosystem that can inform enterprise-mode evidence verification.
- **RStack connection:** Supports optional signed attestation mode beyond local unsigned development mode.

## AI security references

### OWASP Top 10 for Large Language Model Applications
- **Reference:** OWASP Foundation, *Top 10 for Large Language Model Applications*.
- **URL:** https://owasp.org/www-project-top-10-for-large-language-model-applications/
- **Why it matters to RStack:** AI-assisted SDLC systems are exposed to prompt injection, insecure output handling, excessive agency, sensitive information disclosure, and supply-chain risks.
- **RStack connection:** Supports validator restrictions, untrusted PR gates, protected actions, and cross-harness review.

## AI-SDLC prior art

### Augment Code AI SDLC Framework reference architecture
- **Reference:** Augment Code, *AI SDLC Framework: A CTO Reference Architecture*.
- **URL:** https://www.augmentcode.com/guides/ai-sdlc-framework-reference-architecture
- **Verified page title during research:** `AI SDLC Framework: A CTO Reference Architecture | Augment Code`
- **Verified page description during research:** `See how a five-layer AI SDLC framework structures agents, orchestration, observability, and governance so CTOs can scale AI-assisted delivery.`
- **Why it matters to RStack:** Confirms the market pattern that AI-SDLC platforms need layered agents, orchestration, observability, and governance.
- **RStack connection:** RStack already implements a business-facing version through profiles, Business Hub, contracts, approvals, evidence, and adapters.

### ai-sdlc-framework/ai-sdlc
- **Reference:** `ai-sdlc-framework/ai-sdlc`, public GitHub repository.
- **URL:** https://github.com/ai-sdlc-framework/ai-sdlc
- **Observed repo description:** `Declarative governance framework for AI-augmented software development lifecycles`
- **Observed license:** Apache-2.0
- **Observed comparison snapshot:** 3,819 tracked files, strong formal spec/RFC/gate orientation, 38 workflow files, and extensive TypeScript implementation.
- **Why it matters to RStack:** Provides prior-art patterns worth adapting: Decision Engine, Definition-of-Ready gates, declarative resources, cross-harness review, attestations, drift detection, and untrusted PR gates.
- **RStack connection:** RStack should copy patterns, not exact code, preserving its simpler one-package Business Hub product direction.

## Productivity and delivery research

### METR experienced open-source developer productivity study
- **Reference:** METR, *Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity*.
- **URL:** https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/
- **Verified page description during research:** `We conduct a randomized controlled trial to understand how early-2025 AI tools affect the productivity of experienced open-source developers working on their own repositories. Surprisingly, we find that when developers use AI tools, they take 19% longer...`
- **Why it matters to RStack:** The study is a caution against assuming AI coding tools automatically improve productivity in mature codebases. RStack's claim must be that governance and structure reduce ambiguity and rework, not that AI alone guarantees speed.
- **RStack connection:** Supports the paper problem statement and claims discipline.

### Google DORA 2024 report
- **Reference:** Google Cloud DORA, *Accelerate State of DevOps Report 2024*.
- **URL:** https://dora.dev/research/2024/
- **Verified page description during research:** `DORA is a long running research program that seeks to understand the capabilities that drive software delivery and operations performance.`
- **Why it matters to RStack:** Provides delivery-performance and operational-excellence context for measuring AI-SDLC outcomes.
- **RStack connection:** Supports metrics such as cycle time, validation pass rate, deployment confidence, and reliability.

### Stack Overflow Developer Survey AI section
- **Reference:** Stack Overflow Developer Survey 2024, AI section.
- **URL:** https://survey.stackoverflow.co/2024/ai
- **Why it matters to RStack:** Provides broader developer sentiment and adoption context for AI tools.
- **RStack connection:** Supports background section on trust gaps and need for validation/observability.

## RStack primary sources

### RStack SDLC repository
- **Reference:** `richard-devbot/SDLC-rstack`.
- **URL:** https://github.com/richard-devbot/SDLC-rstack
- **Current audited HEAD:** `b559aa4` — `CodeRabbit Generated Unit Tests: Add generated unit tests (#69)`.
- **Current package:** `rstack-agents@1.8.0`.
- **Why it matters:** Primary source for architecture, implementation, tests, docs, and development history.

### RStack README
- **Reference:** `README.md`.
- **Key claim:** RStack is a governed AI-SDLC operating layer for any coding framework.
- **Lifecycle:** `clarify → plan → spec → approve → build → validate → release-readiness → learn`.

### RStack Mintlify documentation
- **Reference:** `docs/mintlify/`.
- **Why it matters:** Public documentation for installation, Business Hub, profiles, builder/validator sandboxing, adapters, and the SDLC pipeline.

### RStack issue roadmap
- **Reference:** GitHub issues #70-#79.
- **Why it matters:** Primary-source roadmap for the research-backed evolution from package to platform.
Loading
Loading