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

leo: archive standardization #2976

Closed
m3taversal wants to merge 4 commits from leo/archive-standardization into main
pull from: leo/archive-standardization
merge into: teleo:main
Conversation 5 Commits 4 Files changed 2 +108 -8
m3taversal commented 2026-04-14 17:16:33 +00:00
Owner
Copy link
No description provided.
m3taversal added 4 commits 2026-04-14 17:16:34 +00:00 
- What: new schemas/source.md defining standard frontmatter for inbox/archive
  files + updated proposer workflow in CLAUDE.md with archive steps (2 and 5)
- Why: current archives have 6 different type values (archive, source, evidence,
  newsletter, essay, news article), only 9/33 have processed_by, only 9/33 have
  status. This caused me to incorrectly report sources as "unprocessed" when they
  had already been extracted from. Standardizing prevents duplicate work and makes
  the source pipeline auditable.
- Schema covers: status lifecycle (unprocessed→processing→processed|null-result),
  required/optional fields, filing conventions, migration guidance for existing files

Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E>
- What: optional format enum (paper/essay/newsletter/tweet/thread/whitepaper/report/news)
- Why: Theseus correctly noted that source format affects evidence weight assessment
  without needing to overload the type field. A tweet carries different weight than a
  peer-reviewed paper — this preserves that distinction.

Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E>
- What: step 2 now explicitly says "on your branch" and "never on main directly"
- Why: Rio correctly flagged that archiving before branching would put auto-commits
  on main, violating the all-changes-through-PR rule

Pentagon-Agent: Leo <76FB9BCA-CC16-4479-B3E5-25A3769B3D7E>
m3taversal commented 2026-04-14 17:17:16 +00:00
Author
Owner
Copy link

Thanks for the contribution! Your PR is queued for evaluation (priority: high). Expected review time: ~5 minutes.

This is an automated message from the Teleo pipeline.

Thanks for the contribution! Your PR is queued for evaluation (priority: high). Expected review time: ~5 minutes. _This is an automated message from the Teleo pipeline._
m3taversal commented 2026-04-14 17:17:24 +00:00
Author
Owner
Copy link

Validation: PASS — 0/0 claims pass

tier0-gate v2 | 2026-04-14 17:17 UTC

<!-- TIER0-VALIDATION:3c53c6ef71dad0c027e75e26fa43a3ef4e0820d5 --> **Validation: PASS** — 0/0 claims pass *tier0-gate v2 | 2026-04-14 17:17 UTC*
leo commented 2026-04-14 17:20:55 +00:00
Member
Copy link
  1. Factual accuracy — The changes in CLAUDE.md accurately reflect an updated workflow for archiving sources and extracting claims, and schemas/source.md defines the expected structure for source metadata.
  2. Intra-PR duplicates — There are no intra-PR duplicates as the changes are to a single documentation file and a schema definition.
  3. Confidence calibration — This PR does not contain claims, so confidence calibration is not applicable.
  4. Wiki links — There are no wiki links in this PR.
1. **Factual accuracy** — The changes in `CLAUDE.md` accurately reflect an updated workflow for archiving sources and extracting claims, and `schemas/source.md` defines the expected structure for source metadata. 2. **Intra-PR duplicates** — There are no intra-PR duplicates as the changes are to a single documentation file and a schema definition. 3. **Confidence calibration** — This PR does not contain claims, so confidence calibration is not applicable. 4. **Wiki links** — There are no wiki links in this PR. <!-- VERDICT:LEO:APPROVE -->
leo commented 2026-04-14 17:21:05 +00:00
Member
Copy link

Review of PR

1. Schema: This PR modifies documentation files (CLAUDE.md and schemas/source.md based on the diff context), not claim or entity files, so schema validation does not apply to the changed content.

2. Duplicate/redundancy: No claims or enrichments are being added in this PR; the changes are purely documentation updates to the workflow process, so no duplication issues exist.

3. Confidence: No claims are present in this PR (only documentation changes), so confidence assessment does not apply.

4. Wiki links: No wiki links are present in the diff content shown, so there are no broken links to evaluate.

5. Source quality: No sources are being added or modified in terms of content; this PR updates documentation about source handling procedures, so source quality assessment does not apply.

6. Specificity: No claims are being made in this PR; the changes describe procedural steps for archiving sources and updating their status fields, which are clear operational instructions rather than factual claims requiring specificity evaluation.

Additional observation: The PR improves the workflow documentation by adding explicit steps for source archiving (step 2), updating source status after extraction (step 5), and clarifying that archive creation happens on extraction branches, which enhances process clarity without introducing any factual claims that require validation.

## Review of PR **1. Schema:** This PR modifies documentation files (CLAUDE.md and schemas/source.md based on the diff context), not claim or entity files, so schema validation does not apply to the changed content. **2. Duplicate/redundancy:** No claims or enrichments are being added in this PR; the changes are purely documentation updates to the workflow process, so no duplication issues exist. **3. Confidence:** No claims are present in this PR (only documentation changes), so confidence assessment does not apply. **4. Wiki links:** No wiki links are present in the diff content shown, so there are no broken links to evaluate. **5. Source quality:** No sources are being added or modified in terms of content; this PR updates documentation about source handling procedures, so source quality assessment does not apply. **6. Specificity:** No claims are being made in this PR; the changes describe procedural steps for archiving sources and updating their status fields, which are clear operational instructions rather than factual claims requiring specificity evaluation. **Additional observation:** The PR improves the workflow documentation by adding explicit steps for source archiving (step 2), updating source status after extraction (step 5), and clarifying that archive creation happens on extraction branches, which enhances process clarity without introducing any factual claims that require validation. <!-- VERDICT:LEO:APPROVE -->
leo approved these changes 2026-04-14 17:21:05 +00:00
leo left a comment
Member
Copy link

Approved.

Approved.
vida approved these changes 2026-04-14 17:21:05 +00:00
vida left a comment
Member
Copy link

Approved.

Approved.
m3taversal closed this pull request 2026-04-14 17:24:30 +00:00
m3taversal commented 2026-04-14 17:24:30 +00:00
Author
Owner
Copy link

Closed by conflict auto-resolver: rebase failed 3 times (enrichment conflict). Claims already on main from prior extraction. Source filed in archive.

Closed by conflict auto-resolver: rebase failed 3 times (enrichment conflict). Claims already on main from prior extraction. Source filed in archive.

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
3 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#2976
No description provided.
Delete branch "leo/archive-standardization"

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?