Reframe benchmark as TwinBench for public launch

Author: Muhra95

.github/ISSUE_TEMPLATE/submit-results.md

@@ -1,6 +1,6 @@
 ---
 name: Submit Benchmark Results
-about: Submit DTaaS-Bench results for your runtime
+about: Submit TwinBench results for your runtime
 title: "[Results] <Runtime Name> v<Version>"
 labels: results
 ---
@@ -16,7 +16,8 @@ labels: results
 
 ## Benchmark Run
 
-- **DTaaS-Bench Version**: 0.2
+- **TwinBench Version**: 0.2
+- **Run Profile**: local reference / SaaS runtime / multi-tenant-ready
 - **Date**: 
 - **Platform**: 
 - **Harness Command Used**:
@@ -33,6 +34,12 @@ python -m harness.runner --url <URL> --token <TOKEN> --user-id <ID> --name "<Nam
 **Coverage-Adjusted Verified Score**: /100
 **Rating**: 
 
+### Dimension Availability
+
+- **Any partially measured dimensions**:
+- **Any unavailable dimensions**:
+- **Reason codes seen in artifact**:
+
 ### Dimension Scores
 
 | Dimension | Verified | Projected | Coverage |
@@ -53,6 +60,7 @@ python -m harness.runner --url <URL> --token <TOKEN> --user-id <ID> --name "<Nam
 - **Diagnostics attached**: yes/no
 - **Metrics attached**: yes/no
 - **Run manifest attached**: yes/no
+- **Preflight completed**: yes/no
 - **Any runtime/provider incident during run**:
 - **Incident attribution**: runtime / upstream dependency / network / unknown
 - **Notes on projected components**:

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to DTaaS-Bench should be documented in this file.
+All notable changes to TwinBench should be documented in this file.
 
 The format is intentionally simple and release-oriented.
 
@@ -28,3 +28,20 @@ The format is intentionally simple and release-oriented.
 ### Notes
 
 - This release is focused on benchmark trust, open-source readiness, and compatibility with the current Nullalis gateway contract.
+
+## [0.3.0] - 2026-03-25
+
+### Added
+
+- Public-facing TwinBench branding for personal AI assistant runtimes
+- New newcomer docs: getting started, run profiles, preflight, compatibility checklist, glossary, integration paths, and lightweight submission flow
+- Public results index and press kit
+- Outreach packet and outreach target list for competitor and lab wave
+- Dimension-level artifact status and reason code fields
+
+### Changed
+
+- Reframed README and specification around personal AI assistant runtime language
+- Clarified scale fairness: same-session contention is diagnostic, multi-user fanout should provision users first
+- Updated trust model and issue template to distinguish unavailable dimensions from product failure
+- Added provisioning-aware scale benchmark behavior and Nullalis local token discovery flow

CONTRIBUTING.md

@@ -1,10 +1,10 @@
-# Contributing to DTaaS-Bench
+# Contributing to TwinBench
 
-We welcome contributions from the community. Here's how you can help.
+We welcome contributions from the community. TwinBench is meant to be approachable to runtime builders, researchers, and advanced indie teams, not just internal operators.
 
 ## Submit Benchmark Results
 
-The most impactful contribution is running DTaaS-Bench against your runtime and submitting verified results.
+The most impactful contribution is running TwinBench against your runtime and submitting verified results.
 
 1. Run the harness: `python3.10 -m harness.runner --url YOUR_URL --token YOUR_TOKEN --user-id 1 --name "Your Runtime" --output results/your-runtime.json --markdown results/your-runtime.md --html results/your-runtime.html`
 2. Open an issue using the **Submit Results** template
@@ -29,12 +29,18 @@ Recommended submission attachments:
 
 Please also read `docs/TRUST_MODEL.md` before submitting. The goal is not just a high score; it is a result other builders will trust.
 
+If you are new to the repo, start with:
+
+- `docs/GETTING_STARTED.md`
+- `docs/PREFLIGHT.md`
+- `docs/HOW_TO_SUBMIT.md`
+
 ## Propose New Dimensions
 
-If you believe an important DTaaS capability is not covered by the current 10 dimensions, open an issue with:
+If you believe an important personal AI assistant runtime capability is not covered by the current 10 dimensions, open an issue with:
 
 - What the dimension measures
-- Why it matters for DTaaS
+- Why it matters for persistent personal AI assistant runtimes
 - A proposed test protocol
 - How it would be scored
 

PRESSKIT.md

@@ -0,0 +1,32 @@
+# TwinBench Press Kit
+
+## One-Line Description
+
+TwinBench is the open benchmark for personal AI assistant runtimes.
+
+## Category Definition
+
+TwinBench evaluates the runtime category behind persistent personal AI assistants: systems that remember across sessions, act autonomously, stay safe during background turns, and operate over time rather than only answering a single prompt.
+
+## Benchmark Principles
+
+- open and vendor-neutral
+- evidence-first
+- verified and projected scores separated clearly
+- unsupported behavior reported honestly
+- reference runtimes welcomed, not privileged
+
+## Why This Matters
+
+The market has benchmarks for coding agents, memory recall, and task completion, but not for the full runtime behavior expected from a real personal AI assistant. TwinBench is an attempt to define that category publicly and make it measurable.
+
+## Reference Runtime
+
+Nullalis is the current reference runtime because it demonstrates the full-stack behavior TwinBench is trying to name. It is not the owner of the benchmark and should be beatable in public.
+
+## Where to Start
+
+- [README.md](README.md)
+- [docs/GETTING_STARTED.md](docs/GETTING_STARTED.md)
+- [docs/RESULTS_INDEX.md](docs/RESULTS_INDEX.md)
+- [docs/OUTREACH_PACKET.md](docs/OUTREACH_PACKET.md)