Reposition fullsend as organization-agnostic framework

[ralphbean]

Extract konflux-ci-specific content from all core documents (README, vision, roadmap, CLAUDE.md, and 16 problem docs) into a new docs/problems/applied/konflux-ci/ directory.

Core docs are now organization-agnostic, treating fullsend as a general framework for autonomous agentic development applicable to any GitHub-hosted organization. Konflux-ci becomes one downstream consumer with its specifics cordoned in applied/konflux-ci/README.md.

Key changes:

• README.md: Reframed as 'for GitHub-hosted organizations' with new applied/ section in document index
• vision.md: Removed konflux-ci framing, added applied docs pointers
• roadmap.md: Phase 4 now references applied docs for domain specificity
• CLAUDE.md: Updated audience and added 'organization-specific content is cordoned' as a key design decision
• Problem docs: Surgical edits to ~50 passages replacing org-specific references with generic language, adding cross-references to applied/
• New docs/problems/applied/ structure with README explaining the pattern
• New docs/problems/applied/konflux-ci/README.md collecting all extracted specifics organized by problem area

No content was lost - all konflux-ci-specific details (coverage data, architecture repo details, Tekton/PipelineRun specifics, JIRA workflow, security dual-context, etc.) are preserved in the applied doc.

Assisted-by: OpenCode claude-opus-4-6@default

[qodo-code-review]

Review Summary by Qodo

Reposition fullsend as organization-agnostic framework with applied docs structure

✨ Enhancement 📝 Documentation

Walkthroughs

Description

• Repositioned fullsend as organization-agnostic framework applicable to any GitHub-hosted
  organization
• Extracted all konflux-ci-specific content into new docs/problems/applied/konflux-ci/ directory
• Updated core problem documents to use generic language, removing organization-specific references
• Added cross-references to applied docs throughout core documentation for organization-specific
  details

Diagram

flowchart LR
  CoreDocs["Core Problem Docs<br/>(organization-agnostic)"]
  AppliedDocs["Applied Docs<br/>(organization-specific)"]
  KonfluxCI["konflux-ci<br/>Applied Considerations"]
  
  CoreDocs -- "generic patterns" --> AppliedDocs
  AppliedDocs -- "example implementation" --> KonfluxCI
  KonfluxCI -- "cross-references back" --> CoreDocs

Loading

File Changes

1. CLAUDE.md 📝 Documentation +4/-5

Reframed audience and design decisions for generality

CLAUDE.md

---

2. README.md 📝 Documentation +9/-5

Repositioned as general framework with applied docs section

README.md

---

3. docs/landscape.md 📝 Documentation +1/-1

Generalized multi-repo awareness example

docs/landscape.md

---

View more (19)

4. docs/problems/agent-architecture.md 📝 Documentation +5/-5

Generalized dual security context to platform organizations

docs/problems/agent-architecture.md

---

5. docs/problems/agent-compatible-code.md 📝 Documentation +3/-3

Removed konflux-ci specifics, added applied docs reference

docs/problems/agent-compatible-code.md

---

6. docs/problems/agent-infrastructure.md 📝 Documentation +5/-5

Generalized infrastructure choices and integration concerns

docs/problems/agent-infrastructure.md

---

7. docs/problems/applied/README.md 📝 Documentation +16/-0

New directory explaining applied docs pattern and structure

docs/problems/applied/README.md

---

8. docs/problems/applied/konflux-ci/README.md 📝 Documentation +216/-0

Comprehensive applied doc collecting all konflux-ci specifics

docs/problems/applied/konflux-ci/README.md

---

9. docs/problems/architectural-invariants.md 📝 Documentation +21/-19

Generalized architecture repo patterns with applied examples

docs/problems/architectural-invariants.md

---

10. docs/problems/code-review.md 📝 Documentation +4/-9

Generalized security agent concerns to platform organizations

docs/problems/code-review.md

---

11. docs/problems/codebase-context.md 📝 Documentation +12/-10

Generalized architecture documentation patterns

docs/problems/codebase-context.md

---

12. docs/problems/contributor-guidance.md 📝 Documentation +16/-12

Removed konflux-ci specifics, added applied docs examples

docs/problems/contributor-guidance.md

---

13. docs/problems/governance.md 📝 Documentation +1/-1

Generalized governance questions to target organizations

docs/problems/governance.md

---

14. docs/problems/human-factors.md 📝 Documentation +2/-2

Generalized contributor motivation to open source projects

docs/problems/human-factors.md

---

15. docs/problems/intent-representation.md 📝 Documentation +7/-7

Generalized intent systems and JIRA references

docs/problems/intent-representation.md

---

16. docs/problems/performance-verification.md 📝 Documentation +15/-19

Generalized platform-specific challenges with applied references

docs/problems/performance-verification.md

---

17. docs/problems/production-feedback.md 📝 Documentation +20/-36

Generalized platform signals with applied docs examples

docs/problems/production-feedback.md

---

18. docs/problems/repo-readiness.md 📝 Documentation +4/-46

Removed konflux-ci coverage data, added applied docs reference

docs/problems/repo-readiness.md

---

19. docs/problems/security-threat-model.md 📝 Documentation +5/-11

Generalized supply chain protections and threat model

docs/problems/security-threat-model.md

---

20. docs/problems/testing-agents.md 📝 Documentation +2/-2

Removed konflux-ci specific context about lightspeed-evaluation

docs/problems/testing-agents.md

---

21. docs/roadmap.md 📝 Documentation +5/-5

Updated Phase 4 to emphasize domain specificity and applied docs

docs/roadmap.md

---

22. docs/vision.md 📝 Documentation +4/-11

Repositioned vision as general framework applicable to any org

docs/vision.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (1) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. security-threat-model heading level wrong 📘 Rule violation ⚙ Maintainability

Description

docs/problems/security-threat-model.md uses ### Open questions subsections but does not include
any ## Open questions section header as required. Automated checks expecting the exact `## Open
questions` heading will fail for this problem document.

Code

docs/problems/security-threat-model.md[R98-100]

+Drift becomes detectable when you have a declared baseline to measure against. An organization's architecture documentation — ADRs, per-service architecture docs — provides that baseline. See [architectural-invariants.md](architectural-invariants.md) for a full treatment of how agents can consume and enforce these constraints, both at PR time and through periodic drift detection scans.

-Drift from security-relevant invariants (RBAC model, trusted task model, build provenance chain) is a security concern, not just a quality concern.
+Drift from security-relevant invariants (RBAC model, trusted component model, build provenance chain) is a security concern, not just a quality concern.

Evidence

PR Compliance ID 131396 requires a line matching ^## Open questions\s*$; this document only
contains ### Open questions headings (e.g., for Threat 1) and therefore lacks the required section
header format.

Rule 131396: Require an "Open questions" section in each problem document
docs/problems/security-threat-model.md[34-44]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/problems/security-threat-model.md` does not include an exact `## Open questions` heading; it uses `### Open questions` instead. This can fail automated compliance checks that require the exact heading.

## Issue Context
The compliance rule requires the exact header `## Open questions` and at least one non-empty line of content under it.

## Fix Focus Areas
- docs/problems/security-threat-model.md[34-44]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Coverage note typo 🐞 Bug ⚙ Maintainability

Description

The new coverage-data pointer in repo-readiness.md misspells “concrete” as “konkrete”, reducing
clarity and professionalism of this core doc.

Code

docs/problems/repo-readiness.md[5]

+> **Organization-specific coverage data:** For konkrete coverage numbers from downstream consumers, see their applied docs (e.g., [konflux-ci](applied/konflux-ci/)).

Evidence

The newly added blockquote intended to direct readers to applied docs contains the misspelling
“konkrete”.

docs/problems/repo-readiness.md[1-6]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`docs/problems/repo-readiness.md` contains a typo in the new blockquote pointing readers to applied-doc coverage data: “konkrete” should be “concrete”.

### Issue Context
This line is part of the organization-agnostic reframing and appears near the top of the doc, so it’s highly visible.

### Fix Focus Areas
- docs/problems/repo-readiness.md[1-6]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[ralphbean]

Thanks @rh-hemartin!