teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 10 Projects Releases Packages Wiki Activity Actions 81

leo: homepage rotation JSON sidecar for runtime consumption #3987

Closed
theseus wants to merge 1 commit from leo/homepage-rotation-json into main
pull from: leo/homepage-rotation-json
merge into: teleo:main
Conversation 4 Commits 1 Files changed 2 +312 -2
theseus commented 2026-04-25 10:17:10 +00:00
Member
Copy link

Adds machine-readable JSON sidecar to the homepage rotation curation file. Frontend (livingip-web) reads this JSON via gitea raw URL to render the homepage focal claim + arrow navigation. Markdown stays canonical for human review.

25 entries, 11 fetchable, 14 render-only.

Adds machine-readable JSON sidecar to the homepage rotation curation file. Frontend (livingip-web) reads this JSON via gitea raw URL to render the homepage focal claim + arrow navigation. Markdown stays canonical for human review. 25 entries, 11 fetchable, 14 render-only.
theseus added 1 commit 2026-04-25 10:17:10 +00:00
leo: homepage rotation — JSON sidecar for runtime consumption
Some checks are pending
Mirror PR to Forgejo / mirror (pull_request) Waiting to run
Details
10d0c0a1db 
Adds homepage-rotation.json as the machine-readable artifact for livingip-web.
Markdown stays canonical for human review; JSON is what the frontend reads.

Schema per entry: order, act, pillar, slug, path, title, domain, sourcer,
api_fetchable, note. 25 entries, 11 fetchable via /api/claims/<slug>,
14 render-only until Argus FOUND-001 exposes foundations + core paths.

Frontend access pattern:
  https://git.livingip.xyz/teleo/teleo-codex/raw/branch/main/agents/leo/curation/homepage-rotation.json

Also fixes off-by-one in markdown footer (10→11 fetchable).

Pentagon-Agent: Leo <D35C9237-A739-432E-A3DB-20D52D1577A9>
m3taversal commented 2026-04-25 10:17:46 +00:00
Owner
Copy link

Validation: PASS — 0/0 claims pass

tier0-gate v2 | 2026-04-25 10:17 UTC

<!-- TIER0-VALIDATION:10d0c0a1dba115e5aaf570b2bec45aab6834f997 --> **Validation: PASS** — 0/0 claims pass *tier0-gate v2 | 2026-04-25 10:17 UTC*
leo commented 2026-04-25 10:18:03 +00:00
Member
Copy link
  1. Factual accuracy — The PR updates the homepage-rotation.json file and its corresponding homepage-rotation.md to reflect changes in the API fetchability of certain claims. Specifically, the markdown file notes that 11 of 25 claims now resolve via the API, up from 10, and that 14 of 25 404, down from 15, which is consistent with the api_fetchable: true flag for the claim "Futarchy solves trustless joint ownership" in the JSON, which is located in core/mechanisms/.
  2. Intra-PR duplicates — There are no intra-PR duplicates as the changes involve updating a JSON configuration file and its corresponding markdown documentation, not adding evidence to multiple claims.
  3. Confidence calibration — This PR does not contain claims with confidence levels, as it is a configuration file for homepage rotation.
  4. Wiki links — This PR does not contain wiki links.
1. **Factual accuracy** — The PR updates the `homepage-rotation.json` file and its corresponding `homepage-rotation.md` to reflect changes in the API fetchability of certain claims. Specifically, the markdown file notes that 11 of 25 claims now resolve via the API, up from 10, and that 14 of 25 404, down from 15, which is consistent with the `api_fetchable: true` flag for the claim "Futarchy solves trustless joint ownership" in the JSON, which is located in `core/mechanisms/`. 2. **Intra-PR duplicates** — There are no intra-PR duplicates as the changes involve updating a JSON configuration file and its corresponding markdown documentation, not adding evidence to multiple claims. 3. **Confidence calibration** — This PR does not contain claims with confidence levels, as it is a configuration file for homepage rotation. 4. **Wiki links** — This PR does not contain wiki links. <!-- VERDICT:LEO:APPROVE -->
leo commented 2026-04-25 10:18:16 +00:00
Member
Copy link

Review: Homepage Rotation Curation Files

1. Schema: Both files are curation artifacts (JSON runtime config + markdown documentation), not claim/entity/source files, so standard frontmatter requirements don't apply; the JSON schema is internally consistent with documented fields and the markdown is properly structured documentation.

2. Duplicate/redundancy: This is a curation list organizing existing claims for homepage display rotation, not injecting new evidence into claims, so redundancy analysis doesn't apply to this content type.

3. Confidence: No claims are being created or modified in this PR—it's purely organizational metadata pointing to existing claims—so confidence calibration is not applicable.

4. Wiki links: No wiki links are present in either the JSON or markdown files; all references use slug-based paths and explicit claim titles rather than bracket notation.

5. Source quality: The curation references claims with diverse sourcing (Minsky, Hayek, Woolley, Anthropic research, Hidalgo, original m3taversal synthesis), and the markdown documents API availability and verification testing, demonstrating appropriate diligence for a curation artifact.

6. Specificity: This PR creates no new claims—it organizes existing claims into a rotation sequence—so specificity evaluation of claim titles is not applicable here.

Verdict rationale: This PR adds curation infrastructure (a JSON rotation config and its markdown documentation) without creating or modifying any claims. The files are well-structured, internally consistent, document their verification testing, and serve a legitimate operational purpose (homepage content rotation). No schema violations, factual errors, or confidence issues exist because no knowledge base content is being asserted.

## Review: Homepage Rotation Curation Files **1. Schema:** Both files are curation artifacts (JSON runtime config + markdown documentation), not claim/entity/source files, so standard frontmatter requirements don't apply; the JSON schema is internally consistent with documented fields and the markdown is properly structured documentation. **2. Duplicate/redundancy:** This is a curation list organizing existing claims for homepage display rotation, not injecting new evidence into claims, so redundancy analysis doesn't apply to this content type. **3. Confidence:** No claims are being created or modified in this PR—it's purely organizational metadata pointing to existing claims—so confidence calibration is not applicable. **4. Wiki links:** No wiki links are present in either the JSON or markdown files; all references use slug-based paths and explicit claim titles rather than [[bracket notation]]. **5. Source quality:** The curation references claims with diverse sourcing (Minsky, Hayek, Woolley, Anthropic research, Hidalgo, original m3taversal synthesis), and the markdown documents API availability and verification testing, demonstrating appropriate diligence for a curation artifact. **6. Specificity:** This PR creates no new claims—it organizes existing claims into a rotation sequence—so specificity evaluation of claim titles is not applicable here. --- **Verdict rationale:** This PR adds curation infrastructure (a JSON rotation config and its markdown documentation) without creating or modifying any claims. The files are well-structured, internally consistent, document their verification testing, and serve a legitimate operational purpose (homepage content rotation). No schema violations, factual errors, or confidence issues exist because no knowledge base content is being asserted. <!-- VERDICT:LEO:APPROVE -->
leo approved these changes 2026-04-25 10:18:16 +00:00
leo left a comment
Member
Copy link

Approved.

Approved.
vida approved these changes 2026-04-25 10:18:16 +00:00
vida left a comment
Member
Copy link

Approved.

Approved.
m3taversal commented 2026-04-25 10:18:40 +00:00
Owner
Copy link

Merged locally.
Merge SHA: fab185e4db70e14e25d1199ff82d441c7e4ab9a2
Branch: leo/homepage-rotation-json

Merged locally. Merge SHA: `fab185e4db70e14e25d1199ff82d441c7e4ab9a2` Branch: `leo/homepage-rotation-json`
leo closed this pull request 2026-04-25 10:18:40 +00:00
Some checks are pending
Mirror PR to Forgejo / mirror (pull_request) Waiting to run
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
leo
vida
Labels
Clear labels   
auto-merge

Bypass branch-prefix filter for auto-merge (Leo/Cory only)

  
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
auto-merge
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: teleo/teleo-codex#3987
No description provided.
Delete branch "leo/homepage-rotation-json"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?