Skip to content

Commit 857cf6d

Browse files
fermatmindfermatmind
authored
COMPETITOR-ALTERNATIVE-SOURCE-LEDGER-GAP-AUDIT-01: add ledger gap audit
Merged generated-only competitor alternative source ledger gap audit after green checks.
1 parent bd69039 commit 857cf6d

4 files changed

Lines changed: 176 additions & 0 deletions

File tree

‎backend/docs/seo/daily-runs/2026-07-06/competitor-alternative-source-ledger-gap-audit-01/EXECUTIVE_DECISION.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Competitor Alternative Source Ledger Gap Audit Decision
2+
3+
Date: 2026-07-06
4+
5+
PR/task: `COMPETITOR-ALTERNATIVE-SOURCE-LEDGER-GAP-AUDIT-01`
6+
7+
Final verdict: `SOURCE_LEDGER_GAP_AUDIT_READY`
8+
9+
## Decision
10+
11+
Competitor Alternative pages are not source-ready.
12+
13+
The current allowed output is a source ledger gap audit only. No competitor facts, comparison claims, public copy, CMS content, routes, schema, sitemap, `llms`, metadata, canonical, noindex, frontend code, production import, or deployment are authorized.
14+
15+
## Required Before Implementation
16+
17+
Before any Alternative page can be drafted or implemented, the operator must approve:
18+
19+
1. exact competitor set
20+
2. exact source URLs or archived evidence
21+
3. exact claim mapping from each source to each visible page statement
22+
4. legal/claim review outcome
23+
5. backend/CMS authority path
24+
6. indexability and discoverability policy
25+
26+
## Gate Result
27+
28+
The source ledger gate is currently incomplete. Continue to legal/claim review handoff as generated-only, then stop implementation until exact approval.

‎backend/docs/seo/daily-runs/2026-07-06/competitor-alternative-source-ledger-gap-audit-01/NEXT_EXACT_AUTHORIZATION_PROMPTS.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Next Exact Authorization Prompts
2+
3+
## Legal Claim Review Handoff
4+
5+
Authorize `COMPETITOR-ALTERNATIVE-LEGAL-CLAIM-REVIEW-HANDOFF-01` as a generated-only handoff.
6+
7+
Allowed scope:
8+
9+
- Summarize source ledger gaps.
10+
- Create legal/brand claim review checklist.
11+
- Keep implementation held.
12+
13+
Forbidden:
14+
15+
- public copy
16+
- routes
17+
- CMS writes
18+
- comparative claims
19+
- schema
20+
- sitemap or `llms`
21+
- metadata
22+
- canonical/noindex changes
23+
- frontend code
24+
- production import or deploy
25+
26+
## Future Source Capture
27+
28+
Use only after legal/claim handoff:
29+
30+
```text
31+
Authorize COMPETITOR-ALTERNATIVE-SOURCE-CAPTURE-READONLY-01.
32+
33+
Allowed scope:
34+
- capture exact approved source URLs
35+
- record retrieved_at
36+
- map one source to one narrow claim
37+
- produce generated-only ledger draft
38+
39+
Forbidden:
40+
- public page implementation
41+
- copy generation for publication
42+
- claims not directly supported by approved sources
43+
- sitemap/llms/schema/metadata changes
44+
```

‎backend/docs/seo/daily-runs/2026-07-06/competitor-alternative-source-ledger-gap-audit-01/SOURCE_LEDGER_GAP_AUDIT.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Competitor Alternative Source Ledger Gap Audit
2+
3+
Date: 2026-07-06
4+
5+
## Candidate Pages
6+
7+
These candidates remain held:
8+
9+
- 16P alternative
10+
- Truity alternative
11+
- 123test alternative
12+
13+
This audit does not verify or state facts about those competitors. It defines what evidence would be required before any page can exist.
14+
15+
## Required Source Ledger Fields
16+
17+
| Field | Requirement |
18+
| --- | --- |
19+
| `competitor_key` | Stable internal key, for example `16p`, `truity`, or `123test` only after approval |
20+
| `source_url` | Exact public URL or archived source |
21+
| `source_type` | Official page, pricing page, help page, methodology page, terms/policy, public documentation, or approved third-party source |
22+
| `retrieved_at` | Date and time of capture |
23+
| `claim_supported` | One narrow claim supported by this source |
24+
| `allowed_surface` | Page body, comparison table, FAQ, disclaimer, metadata, schema, or none |
25+
| `claim_risk` | low, medium, high |
26+
| `quote_limit` | Short excerpt only when legally safe; otherwise paraphrase |
27+
| `review_owner` | Operator/legal/brand reviewer |
28+
| `approval_status` | held, approved, rejected, expired |
29+
30+
## Source Categories Needed
31+
32+
| Category | Needed for | Current status |
33+
| --- | --- | --- |
34+
| Official product positioning | Any description of what the competitor offers | missing |
35+
| Pricing / free tier / paid tier | Any free-vs-paid comparison | missing |
36+
| Methodology / assessment model | Any method, model, science, or validity comparison | missing |
37+
| Terms / acceptable-use / policy | Any legal, privacy, or usage boundary | missing |
38+
| Public help docs | Any feature availability or account-flow statement | missing |
39+
| FermatMind authority | Any statement about FermatMind offering, free result, claim boundary, and CTA | must come from backend/CMS authority |
40+
| Legal/brand review | Any comparative or alternative framing | missing |
41+
42+
## Forbidden Until Ledger Exists
43+
44+
- "more accurate than"
45+
- "better than"
46+
- "best alternative"
47+
- "official alternative"
48+
- "clinically validated"
49+
- "scientifically proven superior"
50+
- "trusted by more users"
51+
- "free full report" as a competitor comparison unless both sides are source-backed
52+
- "no paywall" as a competitor comparison unless both sides are source-backed
53+
- implied endorsement, affiliation, partnership, certification, or official replacement
54+
55+
## Source-to-Claim Rules
56+
57+
1. One source should support one narrow claim.
58+
2. Every comparative claim needs source coverage for both FermatMind and the competitor.
59+
3. If a competitor source is missing, write `Unknown`, not an inferred comparison.
60+
4. Schema must not contain claims that are not visibly present and source-backed.
61+
5. Metadata must not make stronger claims than body copy.
62+
6. Sitemap and `llms` inclusion requires separate indexability approval.
63+
64+
## Output Status
65+
66+
The source ledger is not ready for implementation. The next allowed card is `COMPETITOR-ALTERNATIVE-LEGAL-CLAIM-REVIEW-HANDOFF-01`.
67+
68+
## Boundary
69+
70+
This audit is not public copy, not a source ledger, and not implementation authorization.

‎backend/docs/seo/daily-runs/2026-07-06/competitor-alternative-source-ledger-gap-audit-01/scan_manifest.json‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
{
2+
"task_id": "COMPETITOR-ALTERNATIVE-SOURCE-LEDGER-GAP-AUDIT-01",
3+
"date": "2026-07-06",
4+
"repo": "fermatmind/fap-api",
5+
"mode": "generated_only_source_ledger_gap_audit",
6+
"final_verdict": "SOURCE_LEDGER_GAP_AUDIT_READY",
7+
"outputs": [
8+
"EXECUTIVE_DECISION.md",
9+
"SOURCE_LEDGER_GAP_AUDIT.md",
10+
"NEXT_EXACT_AUTHORIZATION_PROMPTS.md",
11+
"scan_manifest.json"
12+
],
13+
"candidate_pages_held": [
14+
"16P alternative",
15+
"Truity alternative",
16+
"123test alternative"
17+
],
18+
"ledger_status": {
19+
"source_ledger_ready": false,
20+
"legal_claim_review_ready": false,
21+
"implementation_authorized": false
22+
},
23+
"scope_guard": {
24+
"runtime_mutation": false,
25+
"cms_mutation": false,
26+
"schema_mutation": false,
27+
"sitemap_or_llms_mutation": false,
28+
"frontend_mutation": false,
29+
"production_deploy": false
30+
},
31+
"next_cards": [
32+
"COMPETITOR-ALTERNATIVE-LEGAL-CLAIM-REVIEW-HANDOFF-01"
33+
]
34+
}

0 commit comments

Comments
 (0)