From 5ca5c9a82232c863ec733f58a07c00d0e54e571e Mon Sep 17 00:00:00 2001 From: AdrianGros Date: Fri, 27 Mar 2026 10:46:40 +0100 Subject: [PATCH 1/4] curate presentation pack and discover funding landscape --- README.md | 30 ++-- docs/discovery/README.md | 7 + .../discover_funding_landscape_2026_de.md | 133 ++++++++++++++++++ docs/presentation/README.md | 24 ++++ docs/presentation/architecture-bios.md | 46 ++++++ docs/presentation/pitch-deck-outline.md | 38 +++++ docs/presentation/pitch-mail-template.md | 40 ++++++ docs/presentation/repo-curation-guide.md | 47 +++++++ docs/presentation/team-operating-model.md | 38 +++++ 9 files changed, 394 insertions(+), 9 deletions(-) create mode 100644 docs/discovery/README.md create mode 100644 docs/discovery/discover_funding_landscape_2026_de.md create mode 100644 docs/presentation/README.md create mode 100644 docs/presentation/architecture-bios.md create mode 100644 docs/presentation/pitch-deck-outline.md create mode 100644 docs/presentation/pitch-mail-template.md create mode 100644 docs/presentation/repo-curation-guide.md create mode 100644 docs/presentation/team-operating-model.md diff --git a/README.md b/README.md index a48eeba..12fefd3 100644 --- a/README.md +++ b/README.md @@ -49,7 +49,8 @@ It is most useful when work needs reviewable outputs, explicit scope boundaries, 4. Run the first cycle and record outputs using [framework/core/deliverables.md](framework/core/deliverables.md). 5. Keep the work inside the rules in [governance/guardrails.md](governance/guardrails.md). -**For AI systems:** Load [AI_CONTEXT.md](AI_CONTEXT.md) for a compact structured summary. +**For AI systems:** Start with [runtime/AI_BIOS.md](runtime/AI_BIOS.md) and load only the runtime cards required by the current task and profile. +**General summary:** [AI_CONTEXT.md](AI_CONTEXT.md) remains available as a compact repository overview. **For software implementers:** See [docs/software-reference.md](docs/software-reference.md) for interface contracts and schemas. ## Repository structure @@ -59,6 +60,7 @@ It is most useful when work needs reviewable outputs, explicit scope boundaries, - `framework/templates/` — reusable framework templates - `governance/` — operating rules, evidence boundaries, and policies - `governance/policies/` — machine-readable (YAML) forms of governance rules +- `runtime/` — AI runtime loader, profiles, and short execution cards ### Core method @@ -102,7 +104,16 @@ It is most useful when work needs reviewable outputs, explicit scope boundaries, | File | Purpose | | --- | --- | -| [AI_CONTEXT.md](AI_CONTEXT.md) | Compact structured summary for AI systems | +| [docs/presentation/README.md](docs/presentation/README.md) | Curated human-readable package for demos, partner talks, and funding outreach | +| [docs/presentation/architecture-bios.md](docs/presentation/architecture-bios.md) | DAD-M architecture narrative and BIOS model for decision makers | +| [docs/discovery/discover_funding_landscape_2026_de.md](docs/discovery/discover_funding_landscape_2026_de.md) | Discover artifact: funding options and go-to-market contact paths (DE/EU) | +| [docs/presentation/team-operating-model.md](docs/presentation/team-operating-model.md) | Operating model for a 3-person founder team | +| [docs/presentation/pitch-mail-template.md](docs/presentation/pitch-mail-template.md) | Practical outreach mail template for programs and partners | +| [docs/presentation/pitch-deck-outline.md](docs/presentation/pitch-deck-outline.md) | Presentation structure focused on clarity and evaluability | +| [docs/presentation/repo-curation-guide.md](docs/presentation/repo-curation-guide.md) | Rules to remove duplication and avoid AI-sounding language | +| [runtime/AI_BIOS.md](runtime/AI_BIOS.md) | Runtime loader entry point for AI systems | +| [runtime/file-registry.yaml](runtime/file-registry.yaml) | Runtime document registry with profiles, routes, and opt-in references | +| [AI_CONTEXT.md](AI_CONTEXT.md) | Compact structured summary for humans and general AI overview | | [docs/overview.md](docs/overview.md) | Concise method overview including design assumption | | [docs/methodology.md](docs/methodology.md) | Methodological positioning, design assumption, comparison table | | [docs/getting-started.md](docs/getting-started.md) | Step-by-step first use (7 steps including scope + approval) | @@ -116,13 +127,14 @@ It is most useful when work needs reviewable outputs, explicit scope boundaries, ## Example usage / workflow -1. Define the project brief, safety boundaries, and scope declaration. -2. Break the work into milestones with clear scope, dependencies, and priority. -3. Obtain approval for the milestone plan before starting M1. -4. Run Discover to collect the facts for milestone M1. -5. Run Apply to design the solution within those facts. -6. Run Deploy to implement only the approved design and capture proofs. -7. Run Monitor to validate the result and prepare the next milestone. +1. Choose a runtime load profile and load only the relevant runtime cards. +2. Define the project brief, safety boundaries, and scope declaration. +3. Break the work into milestones with clear scope, dependencies, and priority. +4. Obtain approval for the milestone plan before starting M1. +5. Run Discover to collect the facts for milestone M1. +6. Run Apply to design the solution within those facts. +7. Run Deploy to implement only the approved design and capture proofs. +8. Run Monitor to validate the result and prepare the next milestone. For a concrete public example, see [docs/examples/rbac-case-example.md](docs/examples/rbac-case-example.md). diff --git a/docs/discovery/README.md b/docs/discovery/README.md new file mode 100644 index 0000000..c0beebb --- /dev/null +++ b/docs/discovery/README.md @@ -0,0 +1,7 @@ +# Discovery Artifacts + +This folder contains Discover phase outputs that support strategic decisions. + +Current entry: + +- [discover_funding_landscape_2026_de.md](discover_funding_landscape_2026_de.md) diff --git a/docs/discovery/discover_funding_landscape_2026_de.md b/docs/discovery/discover_funding_landscape_2026_de.md new file mode 100644 index 0000000..aa5b1ce --- /dev/null +++ b/docs/discovery/discover_funding_landscape_2026_de.md @@ -0,0 +1,133 @@ +# Discover Output: Funding and Positioning (DE/EU, 2026) + +```yaml +artifact: discover-output +program: dadm-governance-platform +milestone: M21 +phase: discover +status: reviewed-draft +date: 2026-03-27 +scope: + - funding-fit screening for a 3-person team + - outreach channels for public and semi-public support + - pitch packaging requirements for human reviewers +``` + +## Team baseline + +- Team size: 3 +- Roles: + - Adrian Groszewski (Fachinformatiker, Projektmanager) + - Mischelle (Kauffrau) + - Marrt (Sicherheitsbeauftragter) +- Asset state: framework + functional software platform +- Objective: presentable and fundable growth path, not only concept stage + +## Problem statement + +The team needs a clear and realistic funding path that fits a software platform with governance and security focus, while keeping application overhead manageable for a small team. + +## Candidate funding tracks + +### Track A: Beratungs- und Matching-Einstieg (immediately) + +Purpose: identify best-fit programs before writing large applications. + +- Foerderberatung "Forschung und Innovation" des Bundes +- BMWE/BMWK Foerder- und Finanzierungsberatung +- Foerderdatenbank for program filtering + +Fit: very high, low barrier, should be used first. + +### Track B: Nationale F&E-Foerderung fuer KMU + +Purpose: finance technical platform expansion and validated pilot work. + +- ZIM (BMWK/BMWE family, R&D-oriented SME support) +- KMU-innovativ (BMBF thematic calls; software/security themes can fit) + +Fit: high when legal entity and R&D work packages are clear. + +### Track C: Steuerliche Entlastung fuer F&E + +Purpose: reduce effective R&D costs independent of a single call cycle. + +- Forschungszulage (BSFZ + tax workflow) + +Fit: high for ongoing development with documented R&D activities. + +### Track D: Gruendungs- und Wachstumsfinanzierung + +Purpose: liquidity and growth financing for operational scaling. + +- KfW ERP-Gruenderkredit StartGeld / KMU products + +Fit: medium to high, depends on legal entity age and bank path. + +### Track E: EU scale-up path + +Purpose: larger funding tickets and international validation. + +- EIC Accelerator +- Eurostars + +Fit: medium now, high after stronger traction and KPI proof. + +## Eligibility observations (initial) + +- EXIST is usually strongest for science-linked startup teams; fit depends on university/research linkage. +- ZIM/KMU-innovativ generally require robust project definition and legal/fiscal readiness. +- EIC Accelerator expects strong novelty + growth potential + execution evidence. +- For a 3-person team, application load must be staged to avoid delivery freeze. + +## Main risks + +- Application overhead displaces product execution. +- Claims in pitch material exceed provable maturity. +- Governance/security value is communicated too abstractly. + +## Discover recommendations (next 6-10 weeks) + +1. Run 2 advisory calls first (Foerderberatung + KfW orientation) before selecting grant track. +2. Build one reusable evidence pack: + - product architecture one-pager + - current capability list + - roadmap by quarter + - security and compliance baseline + - team role model and ownership map +3. Submit one primary path and one fallback path: + - Primary: R&D support track (ZIM or KMU-innovativ depending on fit) + - Fallback: Forschungszulage + KfW growth financing +4. Keep EU track as stage-2 after measurable traction. + +## Team operating split for funding work + +- Adrian: technical story, architecture proof, roadmap commitments. +- Mischelle: business case, budget logic, financial planning, partner communication. +- Marrt: security evidence, risk matrix, governance controls, compliance mapping. + +## Open questions for Apply phase + +- Which legal entity and accounting setup is active today? +- Which Bundesland-specific programs can be added as co-financing? +- Which KPI baseline (users, pilots, retention, conversion) is presentation-ready now? +- Which one-sentence "problem -> value -> proof" narrative is final? + +## Source links (official or program-near) + +- Foerderdatenbank Beratungsangebote: + https://www.foerderdatenbank.de/FDB/DE/Service/Beratung/beratung.html +- Foerderberatung Forschung und Innovation contact page: + https://www.foerderdatenbank.de/FDB/Content/DE/Kontakt/F/foerderberatung-forschung-und-innovation.html +- KfW StartGeld overview: + https://www.kfw.de/%C3%9Cber-die-KfW/Newsroom/Aktuelles/StartGeld.html +- EXIST Gruenderstipendium one-pager (BMWE): + https://exist.de/wp-content/uploads/2025/11/BMWE_Onepager_EXIST-Gruendungsstipendium_2025-DE_web-bf.pdf +- KMU-innovativ IKT (Bundesanzeiger publication entry): + https://www.bundesanzeiger.de/pub/de/amtlicher-teil?edition=BAnz+AT+20.12.2021&year=2021 +- BSFZ/Forschungszulage process guidance: + https://www.bescheinigung-forschungszulage.de/dateien/PDF/20240506_Pruefleitfaden_BSFZ_Mai_2024.pdf +- EIC Accelerator (official program entry): + https://eic.ec.europa.eu/eic-funding-opportunities/eic-accelerator_en +- Eurostars (official program page): + https://www.eurekanetwork.org/programmes/eurostars/ diff --git a/docs/presentation/README.md b/docs/presentation/README.md new file mode 100644 index 0000000..ae0c115 --- /dev/null +++ b/docs/presentation/README.md @@ -0,0 +1,24 @@ +# Presentation Pack (Human-Readable) + +This folder is a curated entry point for people who are not yet inside the framework details. + +Use this pack when you need to explain DAD-M as a working software and governance platform in clear business language. + +## Recommended reading order + +1. [architecture-bios.md](architecture-bios.md) +2. [team-operating-model.md](team-operating-model.md) +3. [pitch-deck-outline.md](pitch-deck-outline.md) +4. [pitch-mail-template.md](pitch-mail-template.md) +5. [repo-curation-guide.md](repo-curation-guide.md) + +## What this pack optimizes for + +- minimal repetition across documents +- concrete statements instead of generic claims +- clear separation between current capability and future roadmap +- reviewer-friendly language for partners, investors, and public funding bodies + +## Related discovery artifact + +- [../discovery/discover_funding_landscape_2026_de.md](../discovery/discover_funding_landscape_2026_de.md) diff --git a/docs/presentation/architecture-bios.md b/docs/presentation/architecture-bios.md new file mode 100644 index 0000000..e0ca65a --- /dev/null +++ b/docs/presentation/architecture-bios.md @@ -0,0 +1,46 @@ +# DAD-M Architecture and BIOS Narrative + +## One sentence + +DAD-M is a governance-first delivery platform that turns AI-assisted work into auditable, milestone-based execution. + +## Architecture in plain language + +The platform has five layers: + +1. Method layer: Discover, Apply, Deploy, Monitor as explicit state transitions. +2. Governance layer: rules, approvals, and blocking checkpoints. +3. Runtime layer: context loading, profile routing, and execution cards. +4. Artifact layer: milestone outputs, decision records, and evidence traces. +5. Delivery layer: software implementation, operations, and user-facing workflows. + +## BIOS model for decision makers + +For presentations we use BIOS as a compact framing model: + +- Business: measurable value for teams, customers, and partners. +- Integrity: traceability, reproducibility, and decision accountability. +- Operations: repeatable execution with clear handoffs and monitoring. +- Security: risk boundaries, approval gates, and controlled change behavior. + +## How BIOS maps to DAD-M + +| BIOS area | DAD-M mechanisms | Evidence examples | +| --- | --- | --- | +| Business | milestone planning, scope control, acceptance criteria | approved milestone plan, delivery acceptance logs | +| Integrity | artifact retention, decision records, immutable checkpoints | discover/apply/deploy/monitor outputs, decision artifacts | +| Operations | bootstrap protocol, module profiles, runtime cards | bootstrap artifacts, profile selection records | +| Security | guardrails, severity handling, escalation and rework policy | policy files, issue severity records, escalation traces | + +## Current platform position (for external communication) + +- Framework repository is public and method-complete for practical usage. +- Governance and runtime artifacts are available and cross-linked. +- Software implementation exists and can be demonstrated with real workflows. +- Focus of the next phase: scale readiness, multi-tenant governance, and asset lifecycle controls. + +## What to avoid in a presentation + +- Avoid claiming official certification unless documented. +- Avoid saying "AI does everything"; emphasize controlled collaboration. +- Avoid mixing roadmap assumptions with current production capabilities. diff --git a/docs/presentation/pitch-deck-outline.md b/docs/presentation/pitch-deck-outline.md new file mode 100644 index 0000000..30f69a5 --- /dev/null +++ b/docs/presentation/pitch-deck-outline.md @@ -0,0 +1,38 @@ +# Pitch Deck Outline (10 Slides) + +## Goal + +Explain clearly why DAD-M matters, what already works, and why funding accelerates measurable outcomes. + +## Slide structure + +1. Problem + - Why AI-assisted delivery fails without governance + - Cost of unclear ownership and non-reproducible outputs +2. Solution + - DAD-M as Discover/Apply/Deploy/Monitor operating system + - What is software today vs. what is roadmap +3. Product demo path + - one real workflow from input to monitored outcome +4. Architecture and BIOS + - Business, Integrity, Operations, Security mapping +5. Traction and proof + - current users, pilots, usage signals, qualitative proof +6. Market and customer profile + - who pays, why now, why this approach +7. Competition and differentiation + - what alternatives do, where DAD-M is structurally stronger +8. Funding use plan + - concrete work packages, budget blocks, milestones +9. Team and execution readiness + - role ownership and delivery cadence +10. Ask and next step + - requested support, timeline, and meeting proposal + +## Deck quality checklist + +- each slide has one core message +- no jargon sentence longer than 20 words +- every performance claim has a source or evidence note +- no "future tense" on current capability slides +- final slide includes explicit call to action diff --git a/docs/presentation/pitch-mail-template.md b/docs/presentation/pitch-mail-template.md new file mode 100644 index 0000000..34f6ab6 --- /dev/null +++ b/docs/presentation/pitch-mail-template.md @@ -0,0 +1,40 @@ +# Pitch Mail Template (Funding / Program Contact) + +Use this as a short first-contact email. Keep it under 180 words. + +## Subject options + +- DAD-M Governance Platform - Anfrage zur Programmpassung +- Foerderfit-Check: Governance-first AI Delivery Platform +- Kurzvorstellung und Terminwunsch (F&E-Foerderung) + +## Template + +Hallo [Name/Team], + +wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer AI-assistierte Projektarbeit. Unser Fokus liegt auf nachvollziehbarer Umsetzung mit klaren Meilenstein-Phasen, Entscheidungsprotokollen und Security-Guardrails. + +Kurz zu uns: +- Adrian Groszewski: Fachinformatiker, Projektmanagement, Produkt und Architektur +- Mischelle: Kaufmaennische Leitung, Finanzierung und Partnerkommunikation +- Marrt: Sicherheitsbeauftragter, Risiko- und Compliance-Absicherung + +Wir suchen die passende Foerderlinie fuer den naechsten Skalierungsschritt (Multi-Tenant-Betrieb, Asset-Lifecycle, Governance-Automation) und moechten vor Antragstellung einen Fit-Check mit Ihnen machen. + +Wenn hilfreich, senden wir vorab: +1. One-Pager (Problem, Loesung, Reifegrad) +2. Architektur- und Sicherheitsuebersicht +3. Roadmap und Ressourcenplanung + +Koennen wir dafuer einen kurzen Termin (20-30 Minuten) vereinbaren? + +Viele Gruesse +[Name] +[Rolle] +[Mail] | [Telefon] | [Repo/Website] + +## Attachments for first reply + +1. One-pager PDF +2. 8-10 slide deck +3. Short product demo link diff --git a/docs/presentation/repo-curation-guide.md b/docs/presentation/repo-curation-guide.md new file mode 100644 index 0000000..cea94c8 --- /dev/null +++ b/docs/presentation/repo-curation-guide.md @@ -0,0 +1,47 @@ +# Repo Curation Guide (No Repetition, No AI-Speak) + +## Objective + +Make the repository easy to trust for human reviewers in under 10 minutes. + +## Curation rules + +1. One concept, one canonical file. +2. Cross-link instead of re-explaining. +3. Replace vague words ("robust", "powerful", "innovative") with evidence. +4. Keep claims falsifiable and time-bounded. +5. Distinguish clearly: + - current capability + - validated next step + - open research question + +## Writing anti-patterns to remove + +- "state-of-the-art" without comparison +- "end-to-end" without boundary definition +- "AI-native" without operational meaning +- repeated summaries across README, overview, and docs + +## Style standard + +- short paragraphs (max 4 lines) +- active voice and concrete verbs +- numbers where possible +- one table per topic, not per paragraph +- one glossary term per concept + +## Structural curation checklist + +- README links to one overview, not many competing intros. +- Each folder has one short `README.md` with purpose and entry points. +- Decision logs stay in `docs/decisions/`. +- Presentation assets stay in `docs/presentation/`. +- Discover artifacts stay in `docs/discovery/`. + +## Release checklist for external sharing + +1. Remove duplicate topic pages or convert to links. +2. Verify all external links and contact addresses. +3. Verify no confidential data in examples. +4. Add "what we can prove today" section to README or deck. +5. Run one non-team readability review before publishing. diff --git a/docs/presentation/team-operating-model.md b/docs/presentation/team-operating-model.md new file mode 100644 index 0000000..2365237 --- /dev/null +++ b/docs/presentation/team-operating-model.md @@ -0,0 +1,38 @@ +# Team Operating Model (3 People) + +## Principle + +Small team means strict focus: one owner per outcome, no shared ambiguity. + +## Roles and ownership + +| Area | Primary owner | Backup | Output | +| --- | --- | --- | --- | +| Product architecture and technical narrative | Adrian | Marrt | architecture brief, roadmap, demo script | +| Commercial logic and application packaging | Mischelle | Adrian | budget, business plan, partner communication | +| Security and governance evidence | Marrt | Adrian | risk matrix, controls, compliance mapping | + +## Weekly cadence + +1. Monday (45 min): funding and delivery priorities, blocker check. +2. Mid-week (30 min): application progress and evidence readiness. +3. Friday (45 min): review artifacts against submission checklist. + +## RACI for funding workflow + +| Task | Adrian | Mischelle | Marrt | +| --- | --- | --- | --- | +| Program selection | C | A/R | C | +| Technical work packages | A/R | C | C | +| Budget and finance section | C | A/R | I | +| Security/compliance chapter | C | I | A/R | +| Final submission package | A | A/R | R | +| External pitch call | A/R | A/R | C | + +Legend: R = Responsible, A = Accountable, C = Consulted, I = Informed + +## Decision rules + +- No submission without one owner per chapter. +- No claim in pitch material without evidence artifact. +- No roadmap promise without assigned implementation owner. From 312bc4ab933c2884652917e606e62d2329a1a2c3 Mon Sep 17 00:00:00 2001 From: AdrianGros Date: Fri, 27 Mar 2026 10:47:59 +0100 Subject: [PATCH 2/4] add official program links to funding discovery --- docs/discovery/discover_funding_landscape_2026_de.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/discovery/discover_funding_landscape_2026_de.md b/docs/discovery/discover_funding_landscape_2026_de.md index aa5b1ce..4cf731f 100644 --- a/docs/discovery/discover_funding_landscape_2026_de.md +++ b/docs/discovery/discover_funding_landscape_2026_de.md @@ -119,6 +119,10 @@ Fit: medium now, high after stronger traction and KPI proof. https://www.foerderdatenbank.de/FDB/DE/Service/Beratung/beratung.html - Foerderberatung Forschung und Innovation contact page: https://www.foerderdatenbank.de/FDB/Content/DE/Kontakt/F/foerderberatung-forschung-und-innovation.html +- ZIM program portal: + https://www.zim.de/ +- ZIM FAQ FuE-Projekte: + https://www.zim.de/ZIM/Redaktion/DE/FAQ/FuE-Projekte/fue-projekte.html - KfW StartGeld overview: https://www.kfw.de/%C3%9Cber-die-KfW/Newsroom/Aktuelles/StartGeld.html - EXIST Gruenderstipendium one-pager (BMWE): From f36eec354cfe2943c88a4a3469e76a6aaf7827c0 Mon Sep 17 00:00:00 2001 From: AdrianGros Date: Fri, 27 Mar 2026 10:58:29 +0100 Subject: [PATCH 3/4] add pr description one-pager and tailored outreach mail --- README.md | 3 + docs/presentation/README.md | 11 ++-- .../one-pager-dadm-governance-platform.md | 63 +++++++++++++++++++ .../outreach-mail-foerderberatung-bund.md | 41 ++++++++++++ docs/presentation/pr-description.md | 39 ++++++++++++ 5 files changed, 153 insertions(+), 4 deletions(-) create mode 100644 docs/presentation/one-pager-dadm-governance-platform.md create mode 100644 docs/presentation/outreach-mail-foerderberatung-bund.md create mode 100644 docs/presentation/pr-description.md diff --git a/README.md b/README.md index 12fefd3..5b8acfd 100644 --- a/README.md +++ b/README.md @@ -106,10 +106,13 @@ It is most useful when work needs reviewable outputs, explicit scope boundaries, | --- | --- | | [docs/presentation/README.md](docs/presentation/README.md) | Curated human-readable package for demos, partner talks, and funding outreach | | [docs/presentation/architecture-bios.md](docs/presentation/architecture-bios.md) | DAD-M architecture narrative and BIOS model for decision makers | +| [docs/presentation/one-pager-dadm-governance-platform.md](docs/presentation/one-pager-dadm-governance-platform.md) | One-page project summary for advisors, partners, and funders | | [docs/discovery/discover_funding_landscape_2026_de.md](docs/discovery/discover_funding_landscape_2026_de.md) | Discover artifact: funding options and go-to-market contact paths (DE/EU) | | [docs/presentation/team-operating-model.md](docs/presentation/team-operating-model.md) | Operating model for a 3-person founder team | | [docs/presentation/pitch-mail-template.md](docs/presentation/pitch-mail-template.md) | Practical outreach mail template for programs and partners | +| [docs/presentation/outreach-mail-foerderberatung-bund.md](docs/presentation/outreach-mail-foerderberatung-bund.md) | Ready-to-send first outreach mail for federal funding advisory | | [docs/presentation/pitch-deck-outline.md](docs/presentation/pitch-deck-outline.md) | Presentation structure focused on clarity and evaluability | +| [docs/presentation/pr-description.md](docs/presentation/pr-description.md) | Clean pull request description template for this curation package | | [docs/presentation/repo-curation-guide.md](docs/presentation/repo-curation-guide.md) | Rules to remove duplication and avoid AI-sounding language | | [runtime/AI_BIOS.md](runtime/AI_BIOS.md) | Runtime loader entry point for AI systems | | [runtime/file-registry.yaml](runtime/file-registry.yaml) | Runtime document registry with profiles, routes, and opt-in references | diff --git a/docs/presentation/README.md b/docs/presentation/README.md index ae0c115..954a5a8 100644 --- a/docs/presentation/README.md +++ b/docs/presentation/README.md @@ -7,10 +7,13 @@ Use this pack when you need to explain DAD-M as a working software and governanc ## Recommended reading order 1. [architecture-bios.md](architecture-bios.md) -2. [team-operating-model.md](team-operating-model.md) -3. [pitch-deck-outline.md](pitch-deck-outline.md) -4. [pitch-mail-template.md](pitch-mail-template.md) -5. [repo-curation-guide.md](repo-curation-guide.md) +2. [one-pager-dadm-governance-platform.md](one-pager-dadm-governance-platform.md) +3. [team-operating-model.md](team-operating-model.md) +4. [pitch-deck-outline.md](pitch-deck-outline.md) +5. [pitch-mail-template.md](pitch-mail-template.md) +6. [outreach-mail-foerderberatung-bund.md](outreach-mail-foerderberatung-bund.md) +7. [pr-description.md](pr-description.md) +8. [repo-curation-guide.md](repo-curation-guide.md) ## What this pack optimizes for diff --git a/docs/presentation/one-pager-dadm-governance-platform.md b/docs/presentation/one-pager-dadm-governance-platform.md new file mode 100644 index 0000000..64e868a --- /dev/null +++ b/docs/presentation/one-pager-dadm-governance-platform.md @@ -0,0 +1,63 @@ +# One-Pager: DAD-M Governance Platform + +## Elevator statement + +DAD-M is a governance-first software platform for AI-assisted project delivery. It transforms ad-hoc AI work into auditable milestone execution with explicit decision points. + +## Problem + +Teams using AI in project work often face the same failures: + +- analysis, design, implementation, and validation are mixed together +- decisions are hard to trace afterward +- scope drift creates delivery and security risk +- results are difficult to reproduce under review + +## Solution + +DAD-M enforces a four-phase operating model: + +1. Discover (facts) +2. Apply (design) +3. Deploy (execution) +4. Monitor (validation) + +This model is backed by governance controls, runtime profiles, and artifact retention. + +## Why now + +- AI adoption in delivery teams is growing faster than governance maturity. +- Buyers and public stakeholders increasingly require reproducibility and accountability. +- Security and compliance demands are rising in multi-tenant software operations. + +## Current capability + +- Public method repository with core framework and governance artifacts. +- Runtime and profile concept documented and operationally usable. +- Functional software platform available for real workflow demonstrations. +- Active scale roadmap for multi-tenant governance and asset lifecycle controls. + +## BIOS value model + +- Business: shorter path from idea to reviewable delivery. +- Integrity: decision traceability and reproducible artifacts. +- Operations: structured handoffs and milestone-level execution control. +- Security: explicit guardrails, severity handling, and escalation paths. + +## Team + +- Adrian Groszewski: product architecture and project management +- Mischelle: business operations and finance communication +- Marrt: security governance and risk controls + +## What we are asking for + +We are seeking program-fit advisory and growth financing alignment for the next platform stage: + +- primary: R&D funding path (for technical scaling work packages) +- secondary: tax/finance instruments for execution continuity + +## Contact + +- Project contact: Adrian Groszewski +- Repository: https://github.com/AdrianGros/dadm-framework diff --git a/docs/presentation/outreach-mail-foerderberatung-bund.md b/docs/presentation/outreach-mail-foerderberatung-bund.md new file mode 100644 index 0000000..a9f5e1c --- /dev/null +++ b/docs/presentation/outreach-mail-foerderberatung-bund.md @@ -0,0 +1,41 @@ +# Outreach Mail (tailored): Foerderberatung "Forschung und Innovation" des Bundes + +## Target contact + +- Institution: Foerderberatung "Forschung und Innovation" des Bundes +- Email: beratung@foerderinfo.bund.de +- Hotline: 0800 26 23 008 +- Lotsendienst Unternehmen: 0800 26 23 009 + +Source: +https://www.foerderdatenbank.de/FDB/DE/Service/Beratung/beratung.html + +## Subject + +Anfrage Foerderfit-Check: DAD-M Governance-Plattform (3er-Team, funktionsfaehige Software) + +## Mail text + +Sehr geehrtes Team der Foerderberatung "Forschung und Innovation" des Bundes, + +wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer AI-assistierte Projektarbeit. Unser Schwerpunkt liegt auf nachvollziehbarer Umsetzung mit klaren Meilensteinen, Entscheidungsprotokollen und Security-Guardrails. + +Team: +- Adrian Groszewski (Fachinformatiker, Projektmanager) +- Mischelle (Kauffrau) +- Marrt (Sicherheitsbeauftragter) + +Wir moechten vor einer Antragstellung einen Foerderfit-Check durchfuehren und die passende Linie fuer unseren naechsten Skalierungsschritt identifizieren (Multi-Tenant-Betrieb, Asset-Lifecycle, Governance-Automation). + +Wenn sinnvoll, senden wir Ihnen vorab: +1. One-Pager (Problem, Loesung, Reifegrad) +2. Architektur- und Sicherheitsuebersicht +3. Roadmap mit Arbeitspaketen + +Koennen wir dafuer einen kurzen Beratungstermin (20-30 Minuten) vereinbaren? + +Vielen Dank und freundliche Gruesse +Adrian Groszewski +fuer das DAD-M Team +[Mail] | [Telefon] +https://github.com/AdrianGros/dadm-framework diff --git a/docs/presentation/pr-description.md b/docs/presentation/pr-description.md new file mode 100644 index 0000000..a696ad1 --- /dev/null +++ b/docs/presentation/pr-description.md @@ -0,0 +1,39 @@ +# PR Description (ready to paste) + +## Title + +Curate presentation package: architecture narrative, one-pager, and funding outreach assets + +## Why + +The repository needed a clear, human-readable entry path for external reviewers (funding advisors, partners, and non-technical stakeholders). Existing method content is strong, but presentation assets were spread out and not yet packaged as one coherent narrative. + +## What changed + +1. Added a focused presentation package under `docs/presentation/`: + - architecture + BIOS narrative + - team operating model for a 3-person founding team + - pitch deck outline + - practical pitch mail template + - repo curation guide (anti-duplication, anti-buzzword) +2. Added a Discover artifact for funding-fit screening: + - `docs/discovery/discover_funding_landscape_2026_de.md` + - includes staged program strategy (DE/EU), risks, and next actions +3. Updated `README.md` documentation index to surface these assets as first-class entry points. + +## Scope and non-goals + +- In scope: documentation curation, funding discovery packaging, external communication assets. +- Out of scope: method logic changes, policy changes, runtime behavior changes, software implementation changes. + +## Reviewer checklist + +1. Is the new presentation reading path clear in under 10 minutes? +2. Are current capabilities clearly separated from roadmap assumptions? +3. Are funding recommendations realistic for a 3-person team? +4. Are there any duplicate statements that should be replaced by cross-links? + +## Risk notes + +- Program fit can change over time; source links are included and should be rechecked before submission windows. +- Some program pathways depend on legal entity and accounting status, which are intentionally marked as open questions. From 29cb51cee69490fd36adea1c74de96d4bbb0c627 Mon Sep 17 00:00:00 2001 From: AdrianGros Date: Fri, 27 Mar 2026 11:32:51 +0100 Subject: [PATCH 4/4] translate presentation package to german --- docs/presentation/README.md | 20 +++-- docs/presentation/architecture-bios.md | 62 +++++++-------- .../one-pager-dadm-governance-platform.md | 76 +++++++++---------- .../outreach-mail-foerderberatung-bund.md | 14 ++-- docs/presentation/pitch-deck-outline.md | 62 +++++++-------- docs/presentation/pitch-mail-template.md | 28 +++---- docs/presentation/pr-description.md | 52 ++++++------- docs/presentation/repo-curation-guide.md | 70 ++++++++--------- docs/presentation/team-operating-model.md | 50 ++++++------ 9 files changed, 216 insertions(+), 218 deletions(-) diff --git a/docs/presentation/README.md b/docs/presentation/README.md index 954a5a8..1bcfdac 100644 --- a/docs/presentation/README.md +++ b/docs/presentation/README.md @@ -1,10 +1,8 @@ -# Presentation Pack (Human-Readable) +# Praesentationspaket (deutsch) -This folder is a curated entry point for people who are not yet inside the framework details. +Dieser Ordner ist der kuratierte Einstieg fuer Leserinnen und Leser, die DAD-M schnell und klar verstehen sollen. -Use this pack when you need to explain DAD-M as a working software and governance platform in clear business language. - -## Recommended reading order +## Empfohlene Reihenfolge 1. [architecture-bios.md](architecture-bios.md) 2. [one-pager-dadm-governance-platform.md](one-pager-dadm-governance-platform.md) @@ -15,13 +13,13 @@ Use this pack when you need to explain DAD-M as a working software and governanc 7. [pr-description.md](pr-description.md) 8. [repo-curation-guide.md](repo-curation-guide.md) -## What this pack optimizes for +## Ziel des Pakets -- minimal repetition across documents -- concrete statements instead of generic claims -- clear separation between current capability and future roadmap -- reviewer-friendly language for partners, investors, and public funding bodies +- klare Sprache statt Buzzwords +- keine doppelten Erklaerungen +- trennscharf zwischen heutigem Stand und Roadmap +- direkte Nutzbarkeit fuer Partner, Foerderstellen und Gremien -## Related discovery artifact +## Zugehoeriges Discover-Artefakt - [../discovery/discover_funding_landscape_2026_de.md](../discovery/discover_funding_landscape_2026_de.md) diff --git a/docs/presentation/architecture-bios.md b/docs/presentation/architecture-bios.md index e0ca65a..c01068b 100644 --- a/docs/presentation/architecture-bios.md +++ b/docs/presentation/architecture-bios.md @@ -1,46 +1,46 @@ -# DAD-M Architecture and BIOS Narrative +# DAD-M Architektur und BIOS-Narrativ -## One sentence +## Ein Satz -DAD-M is a governance-first delivery platform that turns AI-assisted work into auditable, milestone-based execution. +DAD-M ist eine Governance-first Plattform, die KI-gestuetzte Projektarbeit in pruefbare, meilensteinbasierte Umsetzung ueberfuehrt. -## Architecture in plain language +## Architektur in Klartext -The platform has five layers: +Die Plattform hat fuenf Ebenen: -1. Method layer: Discover, Apply, Deploy, Monitor as explicit state transitions. -2. Governance layer: rules, approvals, and blocking checkpoints. -3. Runtime layer: context loading, profile routing, and execution cards. -4. Artifact layer: milestone outputs, decision records, and evidence traces. -5. Delivery layer: software implementation, operations, and user-facing workflows. +1. Methodenebene: Discover, Apply, Deploy, Monitor als klare Zustandswechsel. +2. Governance-Ebene: Regeln, Freigaben und blockierende Kontrollpunkte. +3. Runtime-Ebene: Kontextladung, Profile und Ausfuehrungskarten. +4. Artefakt-Ebene: Meilenstein-Ergebnisse, Entscheidungen und Evidenz. +5. Delivery-Ebene: Softwarebetrieb, Teamprozesse und Nutzerablaeufe. -## BIOS model for decision makers +## BIOS-Modell fuer Entscheider -For presentations we use BIOS as a compact framing model: +Fuer Praesentationen verwenden wir BIOS als kompaktes Erklaerungsmodell: -- Business: measurable value for teams, customers, and partners. -- Integrity: traceability, reproducibility, and decision accountability. -- Operations: repeatable execution with clear handoffs and monitoring. -- Security: risk boundaries, approval gates, and controlled change behavior. +- Business: messbarer Nutzen fuer Teams, Kunden und Partner. +- Integrity: Nachvollziehbarkeit, Reproduzierbarkeit, Verantwortlichkeit. +- Operations: wiederholbare Umsetzung mit klaren Uebergaben. +- Security: Risikogrenzen, Freigabelogik, kontrolliertes Aenderungsverhalten. -## How BIOS maps to DAD-M +## BIOS-Mapping auf DAD-M -| BIOS area | DAD-M mechanisms | Evidence examples | +| BIOS-Bereich | DAD-M-Mechanismen | Evidenzbeispiele | | --- | --- | --- | -| Business | milestone planning, scope control, acceptance criteria | approved milestone plan, delivery acceptance logs | -| Integrity | artifact retention, decision records, immutable checkpoints | discover/apply/deploy/monitor outputs, decision artifacts | -| Operations | bootstrap protocol, module profiles, runtime cards | bootstrap artifacts, profile selection records | -| Security | guardrails, severity handling, escalation and rework policy | policy files, issue severity records, escalation traces | +| Business | Meilensteinplanung, Scope-Kontrolle, Akzeptanzkriterien | freigegebene Plaene, Abnahmeprotokolle | +| Integrity | Artefakt-Retention, Entscheidungsprotokolle, Kontrollpunkte | Discover/Apply/Deploy/Monitor-Artefakte | +| Operations | Bootstrap-Protokoll, Module, Runtime-Profile | Bootstrap-Nachweise, Profilzuweisungen | +| Security | Guardrails, Severity-Logik, Eskalation und Rework | Policy-Dateien, Severity-Records | -## Current platform position (for external communication) +## Aktueller Plattformstand (extern kommunizierbar) -- Framework repository is public and method-complete for practical usage. -- Governance and runtime artifacts are available and cross-linked. -- Software implementation exists and can be demonstrated with real workflows. -- Focus of the next phase: scale readiness, multi-tenant governance, and asset lifecycle controls. +- Oeffentliches Framework-Repository mit nutzbarer Methodenbasis. +- Governance- und Runtime-Artefakte sind verlinkt und einsetzbar. +- Funktionsfaehige Softwareplattform fuer reale Demo-Workflows vorhanden. +- Naechste Phase: Skalierung auf Multi-Tenant-Betrieb und Asset-Lifecycle-Governance. -## What to avoid in a presentation +## Was wir in Praesentationen vermeiden -- Avoid claiming official certification unless documented. -- Avoid saying "AI does everything"; emphasize controlled collaboration. -- Avoid mixing roadmap assumptions with current production capabilities. +- Keine unbelegten Zertifizierungs- oder Compliance-Aussagen. +- Kein "KI macht alles", sondern kontrollierte Zusammenarbeit. +- Keine Vermischung von heutigem Stand und Zukunfts-Roadmap. diff --git a/docs/presentation/one-pager-dadm-governance-platform.md b/docs/presentation/one-pager-dadm-governance-platform.md index 64e868a..90a6ba4 100644 --- a/docs/presentation/one-pager-dadm-governance-platform.md +++ b/docs/presentation/one-pager-dadm-governance-platform.md @@ -1,63 +1,63 @@ -# One-Pager: DAD-M Governance Platform +# One-Pager: DAD-M Governance-Plattform -## Elevator statement +## Kurzstatement -DAD-M is a governance-first software platform for AI-assisted project delivery. It transforms ad-hoc AI work into auditable milestone execution with explicit decision points. +DAD-M ist eine Governance-first Softwareplattform fuer KI-gestuetzte Projektumsetzung. Sie ueberfuehrt ad-hoc KI-Arbeit in pruefbare Meilenstein-Umsetzung mit klaren Entscheidungsstellen. ## Problem -Teams using AI in project work often face the same failures: +Teams mit KI-Einsatz in Projekten haben oft dieselben Ausfaelle: -- analysis, design, implementation, and validation are mixed together -- decisions are hard to trace afterward -- scope drift creates delivery and security risk -- results are difficult to reproduce under review +- Analyse, Design, Umsetzung und Validierung werden vermischt +- Entscheidungen sind im Nachgang schwer nachvollziehbar +- Umfangsdrift erzeugt Liefer- und Sicherheitsrisiken +- Ergebnisse sind unter Review schlecht reproduzierbar -## Solution +## Loesung -DAD-M enforces a four-phase operating model: +DAD-M erzwingt ein Vier-Phasen-Betriebsmodell: -1. Discover (facts) -2. Apply (design) -3. Deploy (execution) -4. Monitor (validation) +1. Discover (Fakten) +2. Apply (Design) +3. Deploy (Umsetzung) +4. Monitor (Validierung) -This model is backed by governance controls, runtime profiles, and artifact retention. +Dieses Modell wird durch Governance-Kontrollen, Runtime-Profile und Artefakt-Retention getragen. -## Why now +## Warum jetzt -- AI adoption in delivery teams is growing faster than governance maturity. -- Buyers and public stakeholders increasingly require reproducibility and accountability. -- Security and compliance demands are rising in multi-tenant software operations. +- KI-Adoption steigt schneller als Governance-Reife. +- Auftraggeber und Foerderstellen fordern mehr Nachvollziehbarkeit. +- Security- und Compliance-Anforderungen steigen im Multi-Tenant-Betrieb. -## Current capability +## Aktueller Stand -- Public method repository with core framework and governance artifacts. -- Runtime and profile concept documented and operationally usable. -- Functional software platform available for real workflow demonstrations. -- Active scale roadmap for multi-tenant governance and asset lifecycle controls. +- Oeffentliches Methoden-Repository mit Framework- und Governance-Kern. +- Runtime- und Profilkonzept dokumentiert und einsetzbar. +- Funktionsfaehige Softwareplattform fuer reale Demoablaeufe vorhanden. +- Skalierungsroadmap fuer Multi-Tenant-Governance und Asset-Lifecycle aktiv. -## BIOS value model +## BIOS-Wertmodell -- Business: shorter path from idea to reviewable delivery. -- Integrity: decision traceability and reproducible artifacts. -- Operations: structured handoffs and milestone-level execution control. -- Security: explicit guardrails, severity handling, and escalation paths. +- Business: kuerzerer Weg von Idee zu reviewfaehigem Ergebnis. +- Integrity: nachweisbare Entscheidungen und reproduzierbare Artefakte. +- Operations: strukturierte Uebergaben und Meilensteinsteuerung. +- Security: explizite Guardrails, Severity-Logik und Eskalationspfade. ## Team -- Adrian Groszewski: product architecture and project management -- Mischelle: business operations and finance communication -- Marrt: security governance and risk controls +- Adrian Groszewski: Produktarchitektur und Projektsteuerung +- Mischelle: kaufmaennische Steuerung und Finanzierungskommunikation +- Marrt: Security-Governance und Risikokontrollen -## What we are asking for +## Anfrage -We are seeking program-fit advisory and growth financing alignment for the next platform stage: +Wir suchen Programmpassungs-Beratung und passende Wachstumsfinanzierung fuer die naechste Plattformphase: -- primary: R&D funding path (for technical scaling work packages) -- secondary: tax/finance instruments for execution continuity +- primaer: F&E-Foerderpfad fuer technische Skalierungsarbeitspakete +- sekundaer: steuerliche und finanzielle Instrumente fuer Umsetzungsstabilitaet -## Contact +## Kontakt -- Project contact: Adrian Groszewski +- Ansprechpartner: Adrian Groszewski - Repository: https://github.com/AdrianGros/dadm-framework diff --git a/docs/presentation/outreach-mail-foerderberatung-bund.md b/docs/presentation/outreach-mail-foerderberatung-bund.md index a9f5e1c..cb36ac2 100644 --- a/docs/presentation/outreach-mail-foerderberatung-bund.md +++ b/docs/presentation/outreach-mail-foerderberatung-bund.md @@ -1,24 +1,24 @@ -# Outreach Mail (tailored): Foerderberatung "Forschung und Innovation" des Bundes +# Outreach-Mail (zugeschnitten): Foerderberatung "Forschung und Innovation" des Bundes -## Target contact +## Zielkontakt - Institution: Foerderberatung "Forschung und Innovation" des Bundes -- Email: beratung@foerderinfo.bund.de +- E-Mail: beratung@foerderinfo.bund.de - Hotline: 0800 26 23 008 - Lotsendienst Unternehmen: 0800 26 23 009 -Source: +Quelle: https://www.foerderdatenbank.de/FDB/DE/Service/Beratung/beratung.html -## Subject +## Betreff Anfrage Foerderfit-Check: DAD-M Governance-Plattform (3er-Team, funktionsfaehige Software) -## Mail text +## Mailtext Sehr geehrtes Team der Foerderberatung "Forschung und Innovation" des Bundes, -wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer AI-assistierte Projektarbeit. Unser Schwerpunkt liegt auf nachvollziehbarer Umsetzung mit klaren Meilensteinen, Entscheidungsprotokollen und Security-Guardrails. +wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer KI-assistierte Projektarbeit. Unser Schwerpunkt liegt auf nachvollziehbarer Umsetzung mit klaren Meilensteinen, Entscheidungsprotokollen und Security-Guardrails. Team: - Adrian Groszewski (Fachinformatiker, Projektmanager) diff --git a/docs/presentation/pitch-deck-outline.md b/docs/presentation/pitch-deck-outline.md index 30f69a5..6372248 100644 --- a/docs/presentation/pitch-deck-outline.md +++ b/docs/presentation/pitch-deck-outline.md @@ -1,38 +1,38 @@ -# Pitch Deck Outline (10 Slides) +# Pitch-Deck-Struktur (10 Folien) -## Goal +## Ziel -Explain clearly why DAD-M matters, what already works, and why funding accelerates measurable outcomes. +Klar zeigen, warum DAD-M relevant ist, was bereits funktioniert und wofuer die Finanzierung konkret eingesetzt wird. -## Slide structure +## Folienstruktur 1. Problem - - Why AI-assisted delivery fails without governance - - Cost of unclear ownership and non-reproducible outputs -2. Solution - - DAD-M as Discover/Apply/Deploy/Monitor operating system - - What is software today vs. what is roadmap -3. Product demo path - - one real workflow from input to monitored outcome -4. Architecture and BIOS - - Business, Integrity, Operations, Security mapping -5. Traction and proof - - current users, pilots, usage signals, qualitative proof -6. Market and customer profile - - who pays, why now, why this approach -7. Competition and differentiation - - what alternatives do, where DAD-M is structurally stronger -8. Funding use plan - - concrete work packages, budget blocks, milestones -9. Team and execution readiness - - role ownership and delivery cadence -10. Ask and next step - - requested support, timeline, and meeting proposal + - Warum KI-gestuetzte Umsetzung ohne Governance scheitert + - Kosten durch unklare Ownership und fehlende Reproduzierbarkeit +2. Loesung + - DAD-M als Discover/Apply/Deploy/Monitor-Betriebssystem + - Was heute schon produktiv ist, was Roadmap ist +3. Produktdemo-Ablauf + - ein realer Workflow von Eingabe bis Monitor-Ergebnis +4. Architektur und BIOS + - Business, Integrity, Operations, Security in der Praxis +5. Traktion und Nachweise + - Nutzer, Pilotprojekte, Nutzungsdaten, qualitative Evidenz +6. Markt und Zielkunden + - wer zahlt, warum jetzt, warum dieser Ansatz +7. Wettbewerb und Differenzierung + - Alternativen und strukturelle Vorteile von DAD-M +8. Mittelverwendung + - konkrete Arbeitspakete, Budgetbloecke, Meilensteine +9. Team und Umsetzungsfaehigkeit + - Rollen, Ownership, Umsetzungsrhythmus +10. Anfrage und naechster Schritt + - gewuenschte Unterstuetzung, Zeitplan, Terminvorschlag -## Deck quality checklist +## Deck-Qualitaetscheck -- each slide has one core message -- no jargon sentence longer than 20 words -- every performance claim has a source or evidence note -- no "future tense" on current capability slides -- final slide includes explicit call to action +- pro Folie genau eine Kernbotschaft +- keine leeren Buzzwords +- jede Leistungsbehauptung mit Quelle oder Artefakt +- kein Zukunftstext in Folien zum Ist-Stand +- letzte Folie mit klarer Handlungsaufforderung diff --git a/docs/presentation/pitch-mail-template.md b/docs/presentation/pitch-mail-template.md index 34f6ab6..0cfa3ef 100644 --- a/docs/presentation/pitch-mail-template.md +++ b/docs/presentation/pitch-mail-template.md @@ -1,30 +1,30 @@ -# Pitch Mail Template (Funding / Program Contact) +# Pitch-Mail-Vorlage (Foerderung / Programmkontakt) -Use this as a short first-contact email. Keep it under 180 words. +Diese Vorlage ist fuer den Erstkontakt gedacht. Zielumfang: maximal 180 Woerter. -## Subject options +## Betreffoptionen -- DAD-M Governance Platform - Anfrage zur Programmpassung -- Foerderfit-Check: Governance-first AI Delivery Platform -- Kurzvorstellung und Terminwunsch (F&E-Foerderung) +- DAD-M Governance-Plattform - Anfrage zur Programmpassung +- Foerderfit-Check fuer Governance-first KI-Projektumsetzung +- Kurzvorstellung und Terminanfrage (F&E-Foerderung) -## Template +## Vorlage Hallo [Name/Team], -wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer AI-assistierte Projektarbeit. Unser Fokus liegt auf nachvollziehbarer Umsetzung mit klaren Meilenstein-Phasen, Entscheidungsprotokollen und Security-Guardrails. +wir sind ein 3-koepfiges Team und entwickeln mit DAD-M eine funktionsfaehige Governance-Plattform fuer KI-assistierte Projektarbeit. Unser Fokus ist nachvollziehbare Umsetzung mit klaren Meilenstein-Phasen, Entscheidungsprotokollen und Security-Guardrails. Kurz zu uns: - Adrian Groszewski: Fachinformatiker, Projektmanagement, Produkt und Architektur - Mischelle: Kaufmaennische Leitung, Finanzierung und Partnerkommunikation - Marrt: Sicherheitsbeauftragter, Risiko- und Compliance-Absicherung -Wir suchen die passende Foerderlinie fuer den naechsten Skalierungsschritt (Multi-Tenant-Betrieb, Asset-Lifecycle, Governance-Automation) und moechten vor Antragstellung einen Fit-Check mit Ihnen machen. +Wir suchen die passende Foerderlinie fuer den naechsten Skalierungsschritt (Multi-Tenant-Betrieb, Asset-Lifecycle, Governance-Automation) und moechten vor Antragstellung einen Fit-Check mit Ihnen durchfuehren. Wenn hilfreich, senden wir vorab: 1. One-Pager (Problem, Loesung, Reifegrad) 2. Architektur- und Sicherheitsuebersicht -3. Roadmap und Ressourcenplanung +3. Roadmap mit Ressourcenplanung Koennen wir dafuer einen kurzen Termin (20-30 Minuten) vereinbaren? @@ -33,8 +33,8 @@ Viele Gruesse [Rolle] [Mail] | [Telefon] | [Repo/Website] -## Attachments for first reply +## Anlagen fuer die Erstantwort -1. One-pager PDF -2. 8-10 slide deck -3. Short product demo link +1. One-Pager (PDF) +2. Pitch-Deck (8-10 Folien) +3. kurzer Demo-Link diff --git a/docs/presentation/pr-description.md b/docs/presentation/pr-description.md index a696ad1..8df412a 100644 --- a/docs/presentation/pr-description.md +++ b/docs/presentation/pr-description.md @@ -1,39 +1,39 @@ -# PR Description (ready to paste) +# PR-Beschreibung (fertig zum Einfuegen) -## Title +## Titel -Curate presentation package: architecture narrative, one-pager, and funding outreach assets +Praesentationspaket kuratiert: Architektur-Narrativ, One-Pager und Foerder-Outreach -## Why +## Ziel -The repository needed a clear, human-readable entry path for external reviewers (funding advisors, partners, and non-technical stakeholders). Existing method content is strong, but presentation assets were spread out and not yet packaged as one coherent narrative. +Das Repository brauchte einen klaren, deutschsprachigen Einstieg fuer externe Pruefende (Foerderstellen, Partner, nicht-technische Stakeholder). Die Methodenbasis war bereits stark, aber Praesentationsinhalte waren noch nicht als zusammenhaengendes Paket aufbereitet. -## What changed +## Aenderungen -1. Added a focused presentation package under `docs/presentation/`: - - architecture + BIOS narrative - - team operating model for a 3-person founding team - - pitch deck outline - - practical pitch mail template - - repo curation guide (anti-duplication, anti-buzzword) -2. Added a Discover artifact for funding-fit screening: +1. Klares Praesentationspaket unter `docs/presentation/` ergaenzt: + - Architektur- und BIOS-Narrativ + - Team-Betriebsmodell fuer ein 3er-Team + - Pitch-Deck-Struktur + - praktische Pitch-Mail-Vorlage + - Kurationsleitfaden ohne Wiederholungen und Buzzwords +2. Discover-Artefakt zur Foerderfaehigkeitsanalyse eingebunden: - `docs/discovery/discover_funding_landscape_2026_de.md` - - includes staged program strategy (DE/EU), risks, and next actions -3. Updated `README.md` documentation index to surface these assets as first-class entry points. + - mit gestuftem DE/EU-Pfad, Risiken und naechsten Schritten +3. `README.md`-Index aktualisiert, damit diese Inhalte direkt auffindbar sind. -## Scope and non-goals +## Umfang und Abgrenzung -- In scope: documentation curation, funding discovery packaging, external communication assets. -- Out of scope: method logic changes, policy changes, runtime behavior changes, software implementation changes. +- Im Umfang: Dokumentationskurierung, Foerder-Discover-Aufbereitung, externe Kommunikationsbausteine. +- Nicht im Umfang: Methodenlogik, Policies, Runtime-Verhalten, Softwareimplementierung. -## Reviewer checklist +## Review-Checkliste -1. Is the new presentation reading path clear in under 10 minutes? -2. Are current capabilities clearly separated from roadmap assumptions? -3. Are funding recommendations realistic for a 3-person team? -4. Are there any duplicate statements that should be replaced by cross-links? +1. Ist der neue Praesentationspfad in unter 10 Minuten verstaendlich? +2. Sind Ist-Stand und Roadmap klar getrennt? +3. Sind die Foerderempfehlungen fuer ein 3er-Team realistisch? +4. Gibt es noch doppelte Aussagen, die durch Verweise ersetzt werden sollten? -## Risk notes +## Risiko-Hinweise -- Program fit can change over time; source links are included and should be rechecked before submission windows. -- Some program pathways depend on legal entity and accounting status, which are intentionally marked as open questions. +- Programmpassung kann sich aendern; Quellen vor Einreichungsfenstern erneut pruefen. +- Einzelne Foerderpfade haengen von Rechtsform und Buchhaltungsstatus ab; diese Punkte sind bewusst als offen markiert. diff --git a/docs/presentation/repo-curation-guide.md b/docs/presentation/repo-curation-guide.md index cea94c8..4656178 100644 --- a/docs/presentation/repo-curation-guide.md +++ b/docs/presentation/repo-curation-guide.md @@ -1,47 +1,47 @@ -# Repo Curation Guide (No Repetition, No AI-Speak) +# Repo-Kurationsleitfaden (keine Wiederholungen, kein KI-Sprech) -## Objective +## Ziel -Make the repository easy to trust for human reviewers in under 10 minutes. +Das Repository soll fuer menschliche Pruefende in unter 10 Minuten vertrauenswuerdig und verstaendlich sein. -## Curation rules +## Kurationsregeln -1. One concept, one canonical file. -2. Cross-link instead of re-explaining. -3. Replace vague words ("robust", "powerful", "innovative") with evidence. -4. Keep claims falsifiable and time-bounded. -5. Distinguish clearly: - - current capability - - validated next step - - open research question +1. Ein Konzept, eine kanonische Datei. +2. Verlinken statt mehrfach erklaeren. +3. Vage Begriffe durch Evidenz ersetzen. +4. Aussagen pruefbar und zeitlich einordnen. +5. Strikt unterscheiden: + - aktueller Leistungsstand + - validierter naechster Schritt + - offene Fragestellung -## Writing anti-patterns to remove +## Schreibmuster, die wir vermeiden -- "state-of-the-art" without comparison -- "end-to-end" without boundary definition -- "AI-native" without operational meaning -- repeated summaries across README, overview, and docs +- "State of the Art" ohne Vergleich +- "End-to-End" ohne Systemgrenze +- "AI-native" ohne operativen Gehalt +- doppelte Zusammenfassungen in README, Overview und Zusatzseiten -## Style standard +## Sprachstandard -- short paragraphs (max 4 lines) -- active voice and concrete verbs -- numbers where possible -- one table per topic, not per paragraph -- one glossary term per concept +- kurze Absaetze (maximal 4 Zeilen) +- aktive Verben +- konkrete Zahlen, wo moeglich +- pro Thema eine Tabelle, nicht pro Absatz +- ein Glossarbegriff pro Konzept -## Structural curation checklist +## Struktur-Checkliste -- README links to one overview, not many competing intros. -- Each folder has one short `README.md` with purpose and entry points. -- Decision logs stay in `docs/decisions/`. -- Presentation assets stay in `docs/presentation/`. -- Discover artifacts stay in `docs/discovery/`. +- README verweist auf genau einen Haupteinstieg. +- Jeder Ordner hat ein kurzes `README.md` mit Zweck und Einstieg. +- Entscheidungsprotokolle liegen in `docs/decisions/`. +- Praesentationsunterlagen liegen in `docs/presentation/`. +- Discover-Artefakte liegen in `docs/discovery/`. -## Release checklist for external sharing +## Release-Check fuer externe Nutzung -1. Remove duplicate topic pages or convert to links. -2. Verify all external links and contact addresses. -3. Verify no confidential data in examples. -4. Add "what we can prove today" section to README or deck. -5. Run one non-team readability review before publishing. +1. Doppelte Inhaltsseiten entfernen oder in Verweise umwandeln. +2. Alle externen Links und Kontakte pruefen. +3. Keine vertraulichen Daten in Beispielen veroeffentlichen. +4. Abschnitt "Was wir heute nachweisen koennen" in README oder Deck pflegen. +5. Eine Lesbarkeitspruefung durch eine fachfremde Person einholen. diff --git a/docs/presentation/team-operating-model.md b/docs/presentation/team-operating-model.md index 2365237..39ed6f3 100644 --- a/docs/presentation/team-operating-model.md +++ b/docs/presentation/team-operating-model.md @@ -1,38 +1,38 @@ -# Team Operating Model (3 People) +# Team-Betriebsmodell (3 Personen) -## Principle +## Prinzip -Small team means strict focus: one owner per outcome, no shared ambiguity. +Kleines Team bedeutet maximale Klarheit: ein Owner pro Ergebnis, keine unklaren Zustaendigkeiten. -## Roles and ownership +## Rollen und Ownership -| Area | Primary owner | Backup | Output | +| Bereich | Primaer | Backup | Ergebnis | | --- | --- | --- | --- | -| Product architecture and technical narrative | Adrian | Marrt | architecture brief, roadmap, demo script | -| Commercial logic and application packaging | Mischelle | Adrian | budget, business plan, partner communication | -| Security and governance evidence | Marrt | Adrian | risk matrix, controls, compliance mapping | +| Produktarchitektur und Techniknarrativ | Adrian | Marrt | Architekturblatt, Roadmap, Demo-Skript | +| Kaufmaennische Logik und Antragsaufbereitung | Mischelle | Adrian | Budget, Business Case, Partnerkommunikation | +| Security- und Governance-Evidenz | Marrt | Adrian | Risikomatrix, Kontrollnachweise, Compliance-Mapping | -## Weekly cadence +## Wochenrhythmus -1. Monday (45 min): funding and delivery priorities, blocker check. -2. Mid-week (30 min): application progress and evidence readiness. -3. Friday (45 min): review artifacts against submission checklist. +1. Montag (45 Min): Prioritaeten, Foerderpfad, Blocker. +2. Mittwoch (30 Min): Stand der Antragsbausteine und Evidenzluecken. +3. Freitag (45 Min): Review gegen Einreichungs-Checkliste. -## RACI for funding workflow +## RACI fuer Foerderworkflow -| Task | Adrian | Mischelle | Marrt | +| Aufgabe | Adrian | Mischelle | Marrt | | --- | --- | --- | --- | -| Program selection | C | A/R | C | -| Technical work packages | A/R | C | C | -| Budget and finance section | C | A/R | I | -| Security/compliance chapter | C | I | A/R | -| Final submission package | A | A/R | R | -| External pitch call | A/R | A/R | C | +| Programmauswahl | C | A/R | C | +| Technische Arbeitspakete | A/R | C | C | +| Budget- und Finanzteil | C | A/R | I | +| Security-/Compliance-Kapitel | C | I | A/R | +| Finale Einreichung | A | A/R | R | +| Externer Pitch-Termin | A/R | A/R | C | -Legend: R = Responsible, A = Accountable, C = Consulted, I = Informed +Legende: R = Responsible, A = Accountable, C = Consulted, I = Informed -## Decision rules +## Entscheidungsregeln -- No submission without one owner per chapter. -- No claim in pitch material without evidence artifact. -- No roadmap promise without assigned implementation owner. +- Kein Versand ohne klaren Owner je Kapitel. +- Keine Behauptung ohne belegbares Artefakt. +- Kein Roadmap-Versprechen ohne Umsetzungsverantwortung.