diff --git a/solutions/tools/hedera-harness/index.mdx b/solutions/tools/hedera-harness/index.mdx
new file mode 100644
index 00000000..6dd52bdb
--- /dev/null
+++ b/solutions/tools/hedera-harness/index.mdx
@@ -0,0 +1,239 @@
+---
+title: "Hedera Harness"
+description: "Describe a Hedera demo in a PRD, then let an agent build a Scaffold HBAR template and check that it works."
+---
+
+## What is Hedera Harness?
+
+Hedera Harness helps you turn a product idea into a working [Scaffold HBAR](/solutions/tools/scaffold-hbar/index) template — and prove that template actually runs.
+
+You write a short product brief (PRD) and a few validation rules for *your* Hedera demo. The harness seeds a clean workspace, asks an AI coding agent to build the template, then checks the result. If something fails, it feeds the failures back to the agent and tries again until the checks pass or the attempt budget runs out.
+
+Use it to:
+
+- Go from PRD → runnable Scaffold HBAR workspace without hand-writing the whole template
+- **Extend** an already-scaffolded app in place (`.harness/` + `yarn harness:extend`) without re-seeding
+- Catch structural, UI, semantic, and optional on-chain issues before you share the template
+- Keep each attempt isolated under `runs/` (or `.harness/runs/` for extend) so you can inspect what the agent produced
+
+
+
+ Clone the harness, copy the skeleton, and run your first Tier 0–1 loop
+
+
+ Scaffold once, then `yarn harness:extend` against `.harness/`
+
+
+ Seed, vendor, generate, validate, and repair at a glance
+
+
+ Source, examples, and authoring guide
+
+
+
+---
+
+## How it relates to Scaffold HBAR
+
+| Tool | Role |
+|------|------|
+| **[Scaffold HBAR](/solutions/tools/scaffold-hbar/index)** | Interactive CLI that scaffolds a Hedera monorepo (contracts, Next.js, network config) from templates |
+| **Hedera Harness** | Takes your PRD, asks an agent to build or extend a Hedera demo compatible with scaffold-hbar templates, then validates the result |
+
+Scaffold provisions apps for humans. The harness asks an agent to produce (or extend) a template from your brief, then checks whether it works. Skills default to the public [hedera-skills](https://github.com/hedera-dev/hedera-skills) repo; greenfield `run` seeds from public [scaffold-hbar](https://github.com/hedera-dev/scaffold-hbar).
+
+---
+
+## Prerequisites
+
+Before using Hedera Harness, ensure you have:
+
+- **Node.js** ≥ 20 — [nodejs.org](https://nodejs.org/)
+- **Git** — [git-scm.com](https://git-scm.com/)
+- **Yarn** (seeded workspaces are Yarn-based):
+ ```bash
+ corepack enable && corepack prepare yarn@stable --activate
+ ```
+- **Cursor CLI** (`agent` on your `PATH`, authenticated) — or another agent CLI you configure in the spec
+- A **product idea** written as a PRD (start from the skeleton in the repo)
+
+
+Tier 3.5 on-chain validation is optional. It needs a funded Hedera **testnet** account created with an **ECDSA** key (not ED25519). Export `HEDERA_OPERATOR_ID` and `HEDERA_OPERATOR_KEY` in the shell that runs the harness — never write those into a generated workspace.
+
+
+---
+
+## Quick Start
+
+### 1. Clone and install
+
+```bash
+git clone https://github.com/hedera-dev/hedera-harness.git
+cd hedera-harness
+npm install
+```
+
+### 2. Copy the skeleton for your idea
+
+```bash
+NAME=my-hedera-demo
+
+cp skeletons/new-template/prd.md docs/prds/${NAME}.md
+cp skeletons/new-template/spec.yaml specs/${NAME}.yaml
+cp skeletons/new-template/acceptance-contract.json contracts/${NAME}-acceptance.json
+cp skeletons/new-template/static.json validators/${NAME}-static.json
+cp skeletons/new-template/yarn.json validators/${NAME}-yarn.json
+cp skeletons/new-template/playwright-smoke.yaml playwright/${NAME}-smoke.yaml
+
+# Align internal paths / names with $NAME (macOS; on Linux drop the '').
+sed -i '' "s/my-template/${NAME}/g" \
+ specs/${NAME}.yaml \
+ validators/${NAME}-static.json \
+ validators/${NAME}-yarn.json \
+ contracts/${NAME}-acceptance.json \
+ playwright/${NAME}-smoke.yaml
+```
+
+### 3. Write the PRD and fill remaining placeholders
+
+1. Rewrite `docs/prds/${NAME}.md` for your product (goal, journeys, Hedera services, non-goals).
+2. Edit `specs/${NAME}.yaml`: fill remaining `REPLACE_ME` stubs. `seed.repo` already defaults to the public scaffold-hbar remote.
+3. Keep Tier 2 / 3 / 3.5 commented until Tier 0–1 passes.
+
+### 4. Run the harness
+
+```bash
+npm run harness -- run specs/${NAME}.yaml --max-attempts 3
+```
+
+Artifacts land under `runs/` (workspace, logs, report).
+
+
+Example PRDs and specs ship in the repo (Proof Wall, HTS precompile, x402) as **inspiration only**. You do not need to run them to use the harness. See the [repository README](https://github.com/hedera-dev/hedera-harness) for the full CLI reference.
+
+
+---
+
+## Extend an existing app
+
+Prefer this path when a Scaffold HBAR template already ships a `.harness/` recipe (for example the Learn-page pilot on `hedera-demo`).
+
+### 1. Scaffold and install
+
+```bash
+npx create-scaffold-hbar@latest
+cd my-app
+yarn install
+```
+
+### 2. Confirm the extend recipe
+
+Templates that support in-place extend include:
+
+- `.harness/spec.yaml` — no `seed`; includes `extend.baseline`
+- `.harness/prd.md` — product brief for the delta
+- `.harness/validators/` — static + yarn gates
+- `package.json` script: `"harness:extend": "hedera-harness extend .harness/spec.yaml"`
+- Dev dependency: `hedera-harness` (optional peers `playwright` / `@hiero-ledger/sdk` only if you enable Tier 2 / 3.5)
+
+### 3. Run extend
+
+```bash
+yarn harness:extend
+```
+
+The harness uses the project directory as the workspace (no re-seed), runs baseline commands, asks the agent to implement the PRD, then validates enabled tiers. Artifacts land under `.harness/runs/`.
+
+Author a new extend recipe with the [hedera-skills hedera-harness plugin](https://github.com/hedera-dev/hedera-skills) (`/create-harness-spec` detects scaffolded apps and emits under `.harness/`).
+
+
+Greenfield `run` (clone the harness repo) and in-place `extend` share the same validation tiers. Only layout and CLI entrypoint differ.
+
+
+---
+
+## How it works
+
+Each run follows a vertical happy path. Skip validation tiers that are not enabled in the spec. On validation failure with attempts remaining, the harness repairs and returns to **Generate**.
+
+
+ 
+
+
+| Stage | What happens |
+|-------|----------------|
+| **Seed** | Clone pinned scaffold-hbar ref into an isolated workspace; optional yarn preflight |
+| **Vendor** | Fetch skills (default: hedera-skills) and copy PRD / contract context into the workspace |
+| **Generate** | Agent CLI builds the template from the PRD |
+| **Oracle audit** | Informational check for peeking — never blocks a pass |
+| **Validate** | Enabled tiers in order (see below) |
+| **Outcome** | Pass, fail (budget exhausted), or infra abort → `runs/` |
+
+
+
+Actors: CLI, Harness, Git sources, Workspace, Generator, Validators.
+
+
+ 
+
+
+
+
+---
+
+## Validation tiers
+
+**Pass condition:** every validation tier enabled in the spec must pass.
+
+| Tier | Spec fields | What it checks |
+|------|-------------|----------------|
+| **0–1 Deterministic** | `validators.static`, `validators.commands`, `requiredFiles`, `forbiddenFiles`, `secretScan` | Files, JSON/text assertions, secrets, yarn install/lint/build (or your commands) |
+| **2 Playwright gate** | `validators.playwright` | Dev server boots; configured routes return OK; optional console / forbidden-text checks |
+| **3 Semantic** | `contract` + `validator` | Read-only agent drives the live app and grades numbered acceptance assertions |
+| **3.5 On-chain** | `chainValidation` (+ Tier 3) | Ephemeral funded ECDSA test signer injected as burner wallet; real txs verified via mirror node |
+
+Tier 0–1 is the minimum. Tier 2–3 are optional but recommended for UI demos. The skeleton ships with Tier 2 / 3 / 3.5 commented out so first runs stay simple.
+
+
+Semantic infrastructure failures (for example MCP or browser unavailable) **abort** the repair loop — the harness does not ask the generator to “fix” a missing browser.
+
+
+---
+
+## Author your own idea
+
+The harness is template-agnostic: start from the skeleton (greenfield) or from `.harness/` (extend), not from forking the example demos.
+
+1. Copy skeletons as in [Quick Start](#quick-start), **or** author under `.harness/` as in [Extend an existing app](#extend-an-existing-app).
+2. Follow the checklist in the repo: [authoring-a-template.md](https://github.com/hedera-dev/hedera-harness/blob/main/docs/authoring-a-template.md).
+3. Enable higher tiers only after Tier 0–1 is green (`npx playwright install chromium` for Tier 2; Playwright MCP + acceptance contract for Tier 3).
+
+Private WIP PRDs can live under `docs/prds/local/` in a local clone (that path is gitignored).
+
+---
+
+## Ecosystem
+
+
+
+ Scaffold Hedera dApps from the CLI—templates, contracts, Next.js, and Hedera Skills
+
+
+ Shared React components, hooks, and MCP server for AI-assisted development
+
+
+ AI coding assistant skills fetched by the harness into each run
+
+
+ Broader toolkit for building verifiable AI agents on Hedera
+
+
+
+---
+
+## Resources
+
+- [GitHub: hedera-harness](https://github.com/hedera-dev/hedera-harness) — CLI source, examples, and issues
+- [GitHub: scaffold-hbar](https://github.com/hedera-dev/scaffold-hbar) — Seed templates repository
+- [Hedera Portal](https://portal.hedera.com/) — Account creation and testnet faucet
+- [HashScan](https://hashscan.io/) — Block explorer for Hedera
diff --git a/solutions/tools/scaffold-hbar/index.mdx b/solutions/tools/scaffold-hbar/index.mdx
index 0920bf45..2a55feff 100644
--- a/solutions/tools/scaffold-hbar/index.mdx
+++ b/solutions/tools/scaffold-hbar/index.mdx
@@ -22,6 +22,9 @@ Scaffold HBAR is an interactive CLI tool (similar to `create-next-app` or `creat
Shared components, hooks, and MCP server for AI agents
+
+ Turn a product brief into a Scaffold HBAR template and check that it runs
+
Source code and contributing guide
@@ -404,6 +407,9 @@ npx create-scaffold-hbar@latest --yes --skip-hedera-skills
Shared React components and hooks for Hedera dApps, plus an MCP server for AI-assisted development
+
+ Turn a product brief into a Scaffold HBAR template and check that it runs
+
AI coding assistant skills for Hedera development
+
+
+| Stage | What happens |
+|-------|----------------|
+| **Seed** | Clone pinned scaffold-hbar ref into an isolated workspace; optional yarn preflight |
+| **Vendor** | Fetch skills (default: hedera-skills) and copy PRD / contract context into the workspace |
+| **Generate** | Agent CLI builds the template from the PRD |
+| **Oracle audit** | Informational check for peeking — never blocks a pass |
+| **Validate** | Enabled tiers in order (see below) |
+| **Outcome** | Pass, fail (budget exhausted), or infra abort → `runs/` |
+
+
+
+
+