Draft the public claims and experience brief for the future site. It supplies section copy, an 13-claim source/status register, separate Community and Teams CTA states, and an original simulated idea-to-issue-to-review story. The README links to the brief. All copy is explicitly pending owner approval.
The private disclosure review and its idea-to-issue addendum are recorded on private RelayView issue #277, comments 42305 and 42368. It is outside this public branch.
Evidence
Before: The public repo contained only a README and no claims brief or demo story.
After:docs/public-claims-brief.md defines the visitor path, source/status limits, simulation labels, fixture boundaries, and publication gate. The public branch contains no private product source or run evidence.
Checks run
git diff --cached --check — passed before commit.
Focused Python check of the brief — 13 unique claim IDs and eight demo stages, required sections, and local links passed.
git status --short — clean after commit and push.
Build and accessibility checks do not apply to this documentation-only change; issues #4 and #5 own implementation checks.
Documentation disposition
updated: added the public candidate brief and linked it from the README. Private disclosure decisions are recorded only on the private product issue.
Merge Danger
Door: two-way; copy can be revised or reverted before publication.
Blast Radius: editorial guidance for site issues #4–#6. The main risk is mistaking candidate copy for approved publication copy; the brief and README state the approval gate.
Rollback: revert commit b7c18de on the site branch. This does not remove the private review comment.
Reviewer prerequisites
Access to the private relayview repository and issue #277 for source and disclosure review.
Product-owner authority to approve or edit exact pre-release copy and demo scope.
No runtime, service, fixture, or paid account is required.
Expected: the branch contains docs/public-claims-brief.md and the README link.
Manual Test Plan
Action: Read docs/public-claims-brief.md against the current private docs/authoritative/brand.md, product-editions.md, review-roles-and-artifacts.md, ADR 0017, and the private issue #277 publication review.
Expected: Approve or edit every exact pre-release section and claim classification. Stop if a claim suggests an unavailable download, Teams service, trust artifact, integration, or unsupported proof.
Action: Review the eight demo stages, synthetic fixture example, persistent simulation label, and failed-check path in the brief.
Expected: Approve or narrow the earliest disclosure point and exact demo scope before #5 implements it. Confirm the illustrated publication is clearly planned and does not imply an actual Gitea write or autonomous issue pickup. Stop if a detail resembles private product run evidence or proprietary mechanisms.
Action: Confirm the Community and Teams CTA destination states with the owner.
Expected: Until verified destinations exist, both remain plain-text unavailable states. Do not turn either into a link or form by inference.
Failure and recovery
If product documentation changes or the owner rejects a claim, update the brief and repeat the focused claim/link checks on the new head. Do not treat this PR merge as publication approval; record exact owner approval before #4/#5 use the copy.
Post-Merge Cleanup
After reviewed merge and issue closure, the issue worktree may be removed through the issue workflow. Keep the private review on private issue #277.
## Summary
Draft the public claims and experience brief for the future site. It supplies section copy, an 13-claim source/status register, separate Community and Teams CTA states, and an original simulated idea-to-issue-to-review story. The README links to the brief. All copy is explicitly pending owner approval.
The private disclosure review and its idea-to-issue addendum are recorded on private RelayView issue #277, comments 42305 and 42368. It is outside this public branch.
## Evidence
- **Before:** The public repo contained only a README and no claims brief or demo story.
- **After:** `docs/public-claims-brief.md` defines the visitor path, source/status limits, simulation labels, fixture boundaries, and publication gate. The public branch contains no private product source or run evidence.
### Checks run
- `git diff --cached --check` — passed before commit.
- Focused Python check of the brief — 13 unique claim IDs and eight demo stages, required sections, and local links passed.
- `git status --short` — clean after commit and push.
- Build and accessibility checks do not apply to this documentation-only change; issues #4 and #5 own implementation checks.
## Documentation disposition
`updated`: added the public candidate brief and linked it from the README. Private disclosure decisions are recorded only on the private product issue.
## Merge Danger
**Door:** two-way; copy can be revised or reverted before publication.
**Blast Radius:** editorial guidance for site issues #4–#6. The main risk is mistaking candidate copy for approved publication copy; the brief and README state the approval gate.
**Rollback:** revert commit `b7c18de` on the site branch. This does not remove the private review comment.
## Reviewer prerequisites
- Access to the private `relayview` repository and issue #277 for source and disclosure review.
- Product-owner authority to approve or edit exact pre-release copy and demo scope.
- No runtime, service, fixture, or paid account is required.
## Pre-Test Setup
```zsh
git fetch origin
git switch ISSUE-3
git pull --ff-only origin ISSUE-3
```
Expected: the branch contains `docs/public-claims-brief.md` and the README link.
## Manual Test Plan
1. [ ] **Action:** Read `docs/public-claims-brief.md` against the current private `docs/authoritative/brand.md`, `product-editions.md`, `review-roles-and-artifacts.md`, ADR 0017, and the private issue #277 publication review.
**Expected:** Approve or edit every exact pre-release section and claim classification. Stop if a claim suggests an unavailable download, Teams service, trust artifact, integration, or unsupported proof.
2. [ ] **Action:** Review the eight demo stages, synthetic fixture example, persistent simulation label, and failed-check path in the brief.
**Expected:** Approve or narrow the earliest disclosure point and exact demo scope before #5 implements it. Confirm the illustrated publication is clearly planned and does not imply an actual Gitea write or autonomous issue pickup. Stop if a detail resembles private product run evidence or proprietary mechanisms.
3. [ ] **Action:** Confirm the Community and Teams CTA destination states with the owner.
**Expected:** Until verified destinations exist, both remain plain-text unavailable states. Do not turn either into a link or form by inference.
## Failure and recovery
If product documentation changes or the owner rejects a claim, update the brief and repeat the focused claim/link checks on the new head. Do not treat this PR merge as publication approval; record exact owner approval before #4/#5 use the copy.
## Post-Merge Cleanup
After reviewed merge and issue closure, the issue worktree may be removed through the issue workflow. Keep the private review on private issue #277.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Draft the public claims and experience brief for the future site. It supplies section copy, an 13-claim source/status register, separate Community and Teams CTA states, and an original simulated idea-to-issue-to-review story. The README links to the brief. All copy is explicitly pending owner approval.
The private disclosure review and its idea-to-issue addendum are recorded on private RelayView issue #277, comments 42305 and 42368. It is outside this public branch.
Evidence
docs/public-claims-brief.mddefines the visitor path, source/status limits, simulation labels, fixture boundaries, and publication gate. The public branch contains no private product source or run evidence.Checks run
git diff --cached --check— passed before commit.git status --short— clean after commit and push.Documentation disposition
updated: added the public candidate brief and linked it from the README. Private disclosure decisions are recorded only on the private product issue.Merge Danger
Door: two-way; copy can be revised or reverted before publication.
Blast Radius: editorial guidance for site issues #4–#6. The main risk is mistaking candidate copy for approved publication copy; the brief and README state the approval gate.
Rollback: revert commit
b7c18deon the site branch. This does not remove the private review comment.Reviewer prerequisites
relayviewrepository and issue #277 for source and disclosure review.Pre-Test Setup
Expected: the branch contains
docs/public-claims-brief.mdand the README link.Manual Test Plan
Action: Read
docs/public-claims-brief.mdagainst the current privatedocs/authoritative/brand.md,product-editions.md,review-roles-and-artifacts.md, ADR 0017, and the private issue #277 publication review.Expected: Approve or edit every exact pre-release section and claim classification. Stop if a claim suggests an unavailable download, Teams service, trust artifact, integration, or unsupported proof.
Action: Review the eight demo stages, synthetic fixture example, persistent simulation label, and failed-check path in the brief.
Expected: Approve or narrow the earliest disclosure point and exact demo scope before #5 implements it. Confirm the illustrated publication is clearly planned and does not imply an actual Gitea write or autonomous issue pickup. Stop if a detail resembles private product run evidence or proprietary mechanisms.
Action: Confirm the Community and Teams CTA destination states with the owner.
Expected: Until verified destinations exist, both remain plain-text unavailable states. Do not turn either into a link or form by inference.
Failure and recovery
If product documentation changes or the owner rejects a claim, update the brief and repeat the focused claim/link checks on the new head. Do not treat this PR merge as publication approval; record exact owner approval before #4/#5 use the copy.
Post-Merge Cleanup
After reviewed merge and issue closure, the issue worktree may be removed through the issue workflow. Keep the private review on private issue #277.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.