@tangle-network/starter-foundry 0.7.2 → 0.13.0

package/registry/families/agent-runtime-game-designer-ts/files/methodology/player-loop.md

@@ -0,0 +1,143 @@
+# Player Loop Design Template
+
+## Overview
+Design a player loop — the cycle of action → feedback → progression
+that defines moment-to-moment play. A game has nested loops at
+different time scales (seconds, minutes, hours, sessions, weeks);
+this template handles one loop at a time.
+
+## When to use
+Trigger when the user is auditing the core loop, designing a new
+secondary loop, or diagnosing why play feels flat. For one-off
+mechanics, use mechanic-design.md instead.
+
+## Loop scales (pick the scale)
+
+- **Micro / second-level**: input → animation → feedback. ~0.1–2s.
+  (Press jump, character lifts, lands.)
+- **Encounter / minute-level**: enter → resolve → reward. ~1–5min.
+  (Combat encounter, puzzle room, conversation.)
+- **Session / hour-level**: goal-set → progress → success. ~30min–2h.
+  (Quest chain, mission, level.)
+- **Campaign / week-level**: meta-progression. ~10+ hours.
+  (Skill tree fill, faction rep maxed, completion arc.)
+
+The loops must nest: micro feedback should feed encounter outcome
+should feed session goal should feed campaign progression. A loop
+that doesn't feed up is decorative.
+
+## Fields
+
+- **Loop Name** and **Type** (core / secondary / meta).
+- **Scale**: which time scale per the taxonomy above.
+- **Action**: the verb the player performs.
+- **Feedback**:
+  - **Sensory**: VFX, SFX, animation, controller rumble — landing
+    confirmation in milliseconds.
+  - **Mechanical**: state change, score, resource gain.
+  - **Narrative**: dialogue change, world flag flipped, NPC
+    reaction.
+- **Progression**: how the loop evolves with repetition.
+  Difficulty curve, new content unlocked, new mechanics layered,
+  new strategic options revealed.
+- **Reward**: extrinsic (XP, loot, currency) and intrinsic
+  (mastery, expression, fellowship). Pure-extrinsic loops burn
+  out fast; pure-intrinsic loops attract a narrower audience.
+- **Duration**: typical iteration time, with min/max bounds.
+  Loops that exceed 2× expected duration usually have an
+  embedded sub-problem.
+- **Motivation hypothesis** (Self-Determination Theory):
+  autonomy, competence, relatedness — name which the loop is
+  optimized for. Most loops fail because they over-index on
+  competence (challenge) without autonomy or relatedness.
+- **Engagement metric**: completion rate, retention through
+  loop, session length, return rate at next-day, churn point.
+- **Failure / death state**: what happens when the player loses
+  the loop. Ramp-up to recovery, time penalty, narrative
+  reframe. Hostile failure states drive churn.
+- **Trade-offs**: what this loop costs in attention, fatigue,
+  cognitive load, or audience appeal.
+
+## Example (worked)
+
+- **Name**: Combat Loop
+- **Type**: Core / encounter-scale
+- **Scale**: minute-level (30s–2min per encounter)
+- **Action**: engage with weapons + abilities; choose target,
+  ability, position.
+- **Feedback**:
+  - Sensory: hit-flash, sound layered with crit, screen shake on
+    heavy.
+  - Mechanical: HP/resource bars, XP, loot drop.
+  - Narrative: nearby NPCs react, faction rep ticks.
+- **Progression**: enemies layer mechanics every 10 hours
+  (basic → armored → elite shielded → ranged casters); player
+  unlocks tools that counter each layer.
+- **Reward**: XP (extrinsic), gear (extrinsic), mastery
+  (intrinsic — combo discovery), expression (intrinsic — build
+  variety).
+- **Duration**: 30s easy, 90s standard, 3min boss.
+- **Motivation**: competence (skill expression), autonomy
+  (build choice). Relatedness via co-op variant.
+- **Metric**: encounters per session (target ≥8), completion
+  rate ≥85% on standard difficulty, return-to-combat rate
+  next session ≥70%.
+- **Failure**: respawn at last checkpoint, no XP loss, retry
+  the encounter.
+- **Trade-offs**: combat-heavy alienates narrative-focused
+  players; mitigated by skip / lower-difficulty options.
+
+## Common loop failures
+
+1. **No feedback hierarchy.** Big and small wins feel the same;
+   players stop reading the signal.
+2. **Loop too long.** A 7-minute "core" loop is actually a
+   session goal, not a core loop. Shorten or recategorize.
+3. **Reward inflation.** Every encounter rewards loot →
+   meaningless. Stratify rewards (most encounters = currency,
+   some = uniques).
+4. **Punitive failure.** Death state takes 5 minutes to recover
+   → players avoid risk → loop becomes stale.
+5. **Loop doesn't nest.** The encounter doesn't feed a session
+   goal; players don't see why they're doing it.
+6. **One motivator only.** Pure-competence loops are exhausting;
+   pure-autonomy loops can lack stakes; pure-relatedness loops
+   need infrastructure (chat, party, guild).
+
+## Designing the difficulty curve
+
+The loop's progression is its difficulty curve. Use:
+- **Flow-channel** model (Csikszentmihalyi): challenge slightly
+  above skill. Below = boredom; above = anxiety.
+- **Difficulty tiers** with player choice. Don't punish lower
+  difficulty; reward exploration.
+- **Failure-recovery time** as a difficulty axis distinct from
+  challenge intensity.
+
+## Output
+
+```
+:::artifact
+template: player-loop
+loop:
+  name: "..."
+  type: "core" | "secondary" | "meta"
+  scale: "encounter"
+  action: "..."
+  feedback: { sensory: ..., mechanical: ..., narrative: ... }
+  progression: "..."
+  reward: { extrinsic: [...], intrinsic: [...] }
+  duration-target: { min: ..., median: ..., max: ... }
+  motivation: ["competence", "autonomy"]
+  metric: { ... }
+  failure-state: "..."
+  trade-offs: [...]
+:::
+```
+
+## Refusal
+
+- The agent will not approve a loop without a metric or a
+  duration target.
+- The agent will not approve a loop whose extrinsic rewards
+  scale faster than its content can sustain (treadmill warning).

package/registry/families/agent-runtime-game-designer-ts/manifest.json

@@ -0,0 +1,150 @@
+{
+  "id": "agent-runtime-game-designer-ts",
+  "description": "Game designer agent bundle \u2014 designs game mechanics, narrative systems, and player experience loops. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only \u2014 never replaces a professional game studio's creative director, producer, or QA team.",
+  "tags": [
+    "agent-runtime",
+    "game-design",
+    "creative-agent",
+    "advisory",
+    "cloudflare-worker"
+  ],
+  "taxonomy": {
+    "language": "markdown",
+    "runtime": "cloudflare-worker",
+    "surface": "agent-runtime"
+  },
+  "includes": [
+    "agent-base:tangle",
+    "agent-base:secure",
+    "agent-output:blocks",
+    "agent-base:memory",
+    "agent-base:scheduler",
+    "agent-base:mcp-registry",
+    "agent-channels:telegram",
+    "agent-channels:discord",
+    "agent-channels:slack",
+    "agent-channels:whatsapp",
+    "agent-channels:imessage",
+    "agent-channels:gmail",
+    "agent-channels:linear"
+  ],
+  "defaults": {
+    "projectType": "agent-runtime-game-designer",
+    "agentName": "game-designer",
+    "publicVars": [
+      "AGENT_NAME"
+    ],
+    "routes": [
+      {
+        "path": "/api/chat",
+        "auth": "bearer",
+        "callsTools": [
+          "mechanic-design",
+          "narrative-system",
+          "player-loop"
+        ]
+      },
+      {
+        "path": "/api/health",
+        "auth": "none",
+        "callsTools": []
+      }
+    ],
+    "declaredCapabilities": [
+      "mechanic-design",
+      "narrative-system-design",
+      "player-loop-design"
+    ],
+    "runtime": {
+      "sandbox": "tangle",
+      "noNewPrivileges": true,
+      "capDrop": "ALL"
+    },
+    "stakes": "low",
+    "advisoryOnly": true,
+    "outboundDomains": [
+      "api.tangle.tools"
+    ],
+    "secrets": [
+      "TANGLE_API_KEY"
+    ]
+  },
+  "files": [
+    {
+      "source": "files/agent.json",
+      "target": "agent.json"
+    },
+    {
+      "source": "files/AGENTS.md",
+      "target": "AGENTS.md"
+    },
+    {
+      "source": "files/methodology/index.json",
+      "target": "methodology/index.json"
+    },
+    {
+      "source": "files/methodology/mechanic-design.md",
+      "target": "methodology/mechanic-design.md"
+    },
+    {
+      "source": "files/methodology/narrative-system.md",
+      "target": "methodology/narrative-system.md"
+    },
+    {
+      "source": "files/methodology/player-loop.md",
+      "target": "methodology/player-loop.md"
+    },
+    {
+      "source": "files/README.md",
+      "target": "README.md"
+    },
+    {
+      "source": "files/TOOLS.md",
+      "target": "TOOLS.md"
+    }
+  ],
+  "contextHints": {
+    "commands": [],
+    "entrypoints": [
+      "AGENTS.md"
+    ],
+    "extensionPoints": [
+      "templates/",
+      "src/lib/tools/"
+    ]
+  },
+  "tieredKeywords": {
+    "tier1": [
+      "game-designer",
+      "game designer",
+      "game-designer-agent",
+      "game designer agent",
+      "creative-game-designer",
+      "creative game designer",
+      "game-mechanics-designer",
+      "game mechanics designer"
+    ],
+    "tier2": [
+      "mechanic-design",
+      "mechanic design",
+      "narrative-system",
+      "narrative system",
+      "player-loop",
+      "player loop",
+      "game-loop",
+      "game loop",
+      "core-loop",
+      "core loop",
+      "progression-system",
+      "progression system"
+    ],
+    "tier3": [
+      "game design",
+      "game-design"
+    ],
+    "archetypes": [
+      "agent-in-sandbox",
+      "creative-agent"
+    ]
+  }
+}

package/registry/families/agent-runtime-grant-writer-ts/files/AGENTS.md

@@ -0,0 +1,60 @@
+---
+name: grant-writer
+role: Grant writer — draft compelling grant proposals, manage deadlines, and track reporting requirements. Not a substitute for a professional grant writer or fundraising consultant.
+domain: nonprofit-grants
+allowedDomains:
+  - api.tangle.tools
+allowedEnv:
+  - TANGLE_API_KEY
+advisoryOnly: true
+escalationRequired: true
+version: 0.1.0
+---
+
+## Role
+
+You are a grant writer agent. You help nonprofit operators draft compelling grant proposals, manage deadlines, and track reporting requirements. You are **not** a substitute for a professional grant writer or fundraising consultant. You do not have access to the organization's financials, board relationships, or funder history unless the operator provides them. State this limit clearly in the first turn of any new conversation.
+
+## Authoritative skills
+
+When the user's request maps to one of these capabilities, load the corresponding template *before* responding. The templates are the methodology source of truth; trust them over training.
+
+- `grant-proposal-drafting` → `templates/grant-proposal-canvas.md`
+- `deadline-management` → `templates/deadline-tracker.md`
+- `reporting-compliance` → `templates/reporting-template.md`
+
+## Output blocks
+
+Wrap structured deliverables in parseable blocks the host UI renders distinctly:
+
+- `:::artifact` — grant proposal drafts, deadline calendars, reporting checklists, and any other persisted record. Always tag the producing template (e.g. `template: grant-proposal-canvas`).
+- `:::escalation` — emitted whenever a request crosses into territory that requires a real professional (see "Mandatory escalation"). The block names the kind of professional the operator should bring in and the question to bring them.
+- `:::analysis` — short interpretive readouts (e.g. "this funder prioritizes outcomes over activities") that aren't the artifact itself but inform the user's next move.
+
+## Mandatory escalation (advisory boundary)
+
+Run the escalation pattern and emit a `:::escalation` block whenever ANY of these fire:
+
+1. **Financial advice** — budget projections, cost allocation, indirect rate negotiation. → operator's CFO or accountant.
+2. **Legal advice** — grant agreements, compliance with federal regulations (e.g., 2 CFR 200), intellectual property clauses. → operator's legal counsel.
+3. **Funder relationship strategy** — who to ask for a meeting, how to approach a program officer, what to say in a call. → operator's development director or board.
+4. **Anything triggering "I should ask my accountant / lawyer / board"** — if the operator is reaching for a professional, escalate before advising.
+
+Do not silently rationalize past any of these. State the escalation, name the professional, and offer to help the operator **prepare** for that conversation (frame the question, list the documents, draft the ask) — preparation is on-scope; the financial / legal / strategic opinion itself is not.
+
+## What you will NOT do
+
+- Make decisions the operator is accountable for (e.g., which funder to pursue, what budget number to submit).
+- Replace the operator's grant writer, development director, or fundraising consultant.
+- Pretend to know the organization's financials, board relationships, or funder history without asking.
+- Fabricate funder priorities, past funding amounts, or success rates.
+- Give legal, tax, or financial advice (escalate instead).
+
+## What you WILL do
+
+- Draft compelling grant proposals using a structured canvas: problem statement, theory of change, activities, outcomes, evaluation, budget narrative.
+- Help the operator articulate their impact in measurable terms.
+- Maintain a deadline tracker with key dates (LOI, full proposal, reporting).
+- Provide reporting templates aligned to common funder requirements.
+- Ask clarifying questions to fill gaps in the operator's narrative.
+- Pair every escalation-trigger with a concrete handoff: which professional, which document, which question.

package/registry/families/agent-runtime-grant-writer-ts/files/README.md

@@ -0,0 +1,17 @@
+# Grant Writer Agent
+
+An agent-runtime bundle that helps nonprofit operators draft grant proposals, manage deadlines, and track reporting requirements.
+
+## Capabilities
+
+- **Grant Proposal Drafting**: Structured canvas for problem statement, theory of change, activities, outcomes, budget.
+- **Deadline Management**: Track LOI, proposal, and reporting deadlines.
+- **Reporting Compliance**: Templates for interim and final reports.
+
+## Usage
+
+Deploy as a Cloudflare Worker with the Tangle router. Set `TANGLE_API_KEY` in environment variables.
+
+## Advisory Only
+
+This agent is an advisory tool. It does not replace a professional grant writer, accountant, or legal counsel. Always verify outputs with domain experts.

package/registry/families/agent-runtime-grant-writer-ts/files/TOOLS.md

@@ -0,0 +1,23 @@
+# TOOLS — agent-runtime-grant-writer-ts
+
+The bundle inherits all primitives from `agent-base:secure`: `secrets`, `workspace`, `webhook-in`, `webhook-out`, `schedule`, `identity`, `audit`. Plus generic agent tools: `Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`, `WebFetch`.
+
+This file lists **domain-specific tools the operator MAY add** if the deployment needs them. Each entry is intent — not implementation. The agent itself can build any of these on demand using `Bash`/`Write` if the operator hasn't.
+
+## Domain tools the operator may want
+
+Stub list — replace with role-specific entries. Keep ≤10 domain tools per deployment; more is fragmentation. Each tool should be:
+- Single-purpose
+- JSON output
+- ≤100 LOC
+- Listed here when added
+
+| Tool | Intent | Notes |
+|---|---|---|
+| `grant-proposal-drafting` | Concrete tool implementing the `grant-proposal-drafting` capability | Operator implements when needed |
+| `deadline-management` | Concrete tool implementing the `deadline-management` capability | Operator implements when needed |
+| `reporting-compliance` | Concrete tool implementing the `reporting-compliance` capability | Operator implements when needed |
+
+## Build a new tool when you need it
+
+The agent's job includes building tools when the measurement doesn't exist. New tools should be small, JSON-output, single-purpose. Add an entry here via PR after shipping.

package/registry/families/agent-runtime-grant-writer-ts/files/agent.json

@@ -0,0 +1,38 @@
+{
+  "name": "grant-writer",
+  "description": "Grant writer agent bundle — helps nonprofit operators draft compelling grant proposals, manage deadlines, and track reporting requirements. Composes the agent-runtime substrate with structured-output-blocks on the Tangle floor. Advisory only — never replaces a professional grant writer or fundraising consultant.",
+  "version": "0.1.0",
+  "tags": [
+    "agent-runtime",
+    "grant-writing",
+    "nonprofit",
+    "advisory-agent",
+    "cloudflare-worker"
+  ],
+  "prompt": {
+    "systemPromptFile": "AGENTS.md"
+  },
+  "tools": {
+    "filesystem": true,
+    "shell": true,
+    "router": true
+  },
+  "permissions": {
+    "filesystem.write": "ask",
+    "shell.exec": "ask",
+    "network": "ask"
+  },
+  "resources": {
+    "files": [
+      {
+        "source": "methodology/"
+      },
+      {
+        "source": "README.md"
+      },
+      {
+        "source": "TOOLS.md"
+      }
+    ]
+  }
+}

package/registry/families/agent-runtime-grant-writer-ts/files/methodology/deadline-tracker.md

@@ -0,0 +1,140 @@
+# Deadline Tracker Template
+
+## Purpose
+Maintain a single, durable record of every grant cycle a
+nonprofit / lab / writer is engaged with — from prospect through
+final report. Missed deadlines are the most common reason small
+nonprofits forfeit funding they otherwise qualified for.
+
+## When to use
+Trigger when the user is managing more than one or two grant
+relationships, ramping into a new fiscal year, or recovering from
+a missed-deadline near-miss. For proposal-writing itself, route
+to grant-proposal-canvas.md. For final reports, route to
+reporting-template.md.
+
+## Method
+
+1. **Capture the full lifecycle, not just the proposal date.**
+   Each grant has up to seven dates that matter:
+   - Prospect / initial outreach scheduled
+   - LOI (letter of inquiry) due
+   - Full proposal due
+   - Site visit / interview window
+   - Award notification expected
+   - Funds transfer expected
+   - Interim report(s) due
+   - Final report due
+   - Renewal LOI / re-application window
+2. **Pre-deadline buffers.** For each external deadline, add
+   internal milestones:
+   - **2 weeks before**: full draft complete, internal review
+     scheduled.
+   - **1 week before**: review complete, revisions in.
+   - **3 business days before**: final upload / mail.
+   - **Day before**: confirmation of receipt.
+   Working back from the external deadline this way reveals
+   schedule conflicts early.
+3. **Required attachments per funder.** Each funder has its own
+   list, often overlooked:
+   - 501(c)(3) determination letter
+   - Most-recent audited financial statements
+   - Board list with affiliations
+   - Prior 990 (often previous fiscal year)
+   - Project budget in the funder's template
+   - Logic model (some funders require)
+   - Organizational budget
+   - Letters of support from partners
+   - Demographic / impact data
+   Maintain a shared "attachments locker" so each application
+   pulls from one source of truth.
+4. **Status taxonomy.** Use a small, strict set:
+   - **Prospect**: identified, not yet contacted.
+   - **In conversation**: contacted, no application yet.
+   - **LOI submitted** / **Invited** / **Declined-LOI**.
+   - **Drafting**: full proposal in progress.
+   - **Submitted**: filed; awaiting decision.
+   - **Awarded**: funded; in active grant period.
+   - **Declined**: rejected; record reason for next cycle.
+   - **Reporting**: in active reporting; not yet closed.
+   - **Closed**: cycle complete.
+5. **Reminders and ownership.**
+   - Each deadline has a lead and a backup.
+   - Calendar invites set 2 weeks, 1 week, and 3 days before
+     each deadline.
+   - Email reminders to the lead with the attachment checklist.
+6. **Capacity guardrails.**
+   - Track the count of active proposals per development staffer;
+     if any one person has >3 in-flight, the org is over-capacity.
+   - Track total funder-relationships under management; ratio
+     to staff hours.
+7. **Renewal radar.**
+   - Awarded grants typically have re-application windows
+     6–12 months from award. Surface these proactively.
+   - Lapsed multi-year grants need a "would they consider us
+     again" outreach a year before re-applying.
+
+## Master tracker schema (suggested)
+
+| Funder | Program | Cycle | LOI Due | Full Due | Award Date | Award Amount | Reports Due | Status | Lead | Notes |
+|--------|---------|-------|---------|----------|------------|--------------|-------------|--------|------|-------|
+
+Plus a per-funder detail block with:
+- Funder mission alignment (1 sentence)
+- Past relationship (last gift, last decline, contact name)
+- Required attachments (linked to attachments locker)
+- Application URL + login
+- Funder-specific quirks (page limits, font requirements,
+  budget format, narrative themes preferred)
+
+## Common tracker failures
+
+1. **Single-deadline tracking.** Tracking only the proposal due
+   date misses LOI, reports, renewal — many lapses happen here.
+2. **No buffers.** Backing up to the day-of-deadline workflow
+   produces last-minute submissions and missed attachments.
+3. **No attachment locker.** Each application re-creates the
+   same attachments from scratch; one update misses; auditors
+   notice.
+4. **Status drift.** "Submitted" → "...?" — without follow-up
+   discipline, awards and declines aren't recorded; the next
+   cycle has no memory.
+5. **Capacity blind.** Saying yes to every prospect; staff burns
+   out; quality drops; funders notice.
+6. **Lost contact transitions.** When a funder's program officer
+   changes, the relationship hand-off isn't captured; next
+   cycle begins cold.
+
+## Output
+
+```
+:::artifact
+template: deadline-tracker
+period: "FY2026"
+grants:
+  - funder: "..."
+    program: "..."
+    cycle: "2025–2026"
+    loi-due: "2025-09-15"
+    full-due: "2025-11-01"
+    award-date: "2026-02-15 (expected)"
+    requested-amount: $...
+    reports:
+      interim: "2026-08-01"
+      final: "2027-02-01"
+    status: "Drafting"
+    lead: "..."
+    backup: "..."
+    notes: "..."
+upcoming-week: [...]
+upcoming-month: [...]
+overcapacity-flags: [...]
+:::
+```
+
+## Refusal
+
+- The agent will not approve a tracker that omits report dates;
+  reports are how funder relationships sustain.
+- The agent will not push the team toward a higher proposal
+  count when capacity-flags fire.

package/registry/families/agent-runtime-grant-writer-ts/files/methodology/grant-proposal-canvas.md

@@ -0,0 +1,37 @@
+# Grant Proposal Canvas
+
+## 1. Problem Statement
+- What is the specific problem you are addressing?
+- Who is affected? (geography, demographics, scale)
+- Why is this problem urgent now?
+
+## 2. Theory of Change
+- If we do X, then Y will happen because Z.
+- Map inputs → activities → outputs → outcomes → impact.
+
+## 3. Activities
+- What will you do with the grant funds?
+- Timeline: key milestones.
+- Who will execute? (staff, partners, volunteers)
+
+## 4. Outcomes & Evaluation
+- Primary outcome: measurable change.
+- Secondary outcomes.
+- How will you measure success? (indicators, data sources, frequency)
+
+## 5. Budget Narrative
+- Total request.
+- Major line items (personnel, materials, travel, indirect).
+- Justification: why each cost is necessary.
+
+## 6. Organizational Capacity
+- Brief history and mission.
+- Relevant experience (past grants, programs).
+- Key staff qualifications.
+
+## 7. Sustainability
+- How will the work continue after the grant?
+- Other funding sources.
+
+---
+*Use this canvas to structure each proposal. Fill sections with the operator's input. Flag gaps for the operator to address.*

package/registry/families/agent-runtime-grant-writer-ts/files/methodology/index.json

@@ -0,0 +1,25 @@
+{
+  "entries": [
+    {
+      "id": "grant-proposal-canvas",
+      "capability": "grant-proposal-drafting",
+      "path": "./grant-proposal-canvas.md",
+      "tags": ["methodology", "proposal", "logic-model"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "deadline-tracker",
+      "capability": "deadline-management",
+      "path": "./deadline-tracker.md",
+      "tags": ["methodology", "deadlines", "calendar"],
+      "version": "0.1.0"
+    },
+    {
+      "id": "reporting-template",
+      "capability": "reporting-compliance",
+      "path": "./reporting-template.md",
+      "tags": ["methodology", "reporting", "compliance"],
+      "version": "0.1.0"
+    }
+  ]
+}

package/registry/families/agent-runtime-grant-writer-ts/files/methodology/reporting-template.md

@@ -0,0 +1,30 @@
+# Grant Reporting Template
+
+## 1. Executive Summary
+- Brief overview of progress during the reporting period.
+
+## 2. Activities Completed
+- List activities funded by the grant.
+- Include dates, locations, participant numbers.
+
+## 3. Outcomes Achieved
+- Compare against stated outcomes in the proposal.
+- Use quantitative data where possible.
+- Include qualitative stories or testimonials.
+
+## 4. Challenges & Lessons Learned
+- What didn't go as planned?
+- How did you adapt?
+- What would you do differently?
+
+## 5. Financial Report
+- Budget vs actual expenditures.
+- Explain any significant variances.
+- Attach receipts or invoices as required.
+
+## 6. Next Steps
+- Plans for the next reporting period.
+- Any changes to timeline or activities.
+
+---
+*Customize sections based on funder requirements. Attach supporting documents as needed.*