wiki

Incoming Review

wiki/incoming-review.md

Rendered from markdown source. Open raw source on GitHub.

Incoming Review

This page is for newly added files that have been inventoried but not yet classified or moved.

Current state: artifacts/incoming/ is now a mostly flat intake pool of 464 files plus the standalone ipol_package/ ancillary bundle. The earlier branch-folder concentration has already been absorbed into project pages, lineage pages, or archive paths, so this queue should now stay focused on genuinely new intake rather than re-triaging settled branches.

Observed shape:

  • The intake is mostly .md, .docx, and .pdf, with a small number of other companions that should be routed elsewhere when they are clearly auxiliary.
  • artifacts/for-further-routing/ is the landing zone for non-md/pdf/docx items that probably do not belong in the 80% ingestion pass.
  • The dominant remaining work is classification and duplicate collapse, not structure discovery.
  • The SCT, CICP, POLEMEMELOP, WitnessKey, Loopverse, and patent lineages already have stable project shells or lineage pages.
  • Root-level works that were already classified should not be re-listed here.
  • Exact duplicate clones should only be pruned when a surviving copy already exists elsewhere.

Use this page to list:

  • newly witnessed files in artifacts/incoming/;
  • uncertain classifications;
  • proposed moves that still need review.

Files that are plainly personal, or that are clearly not original work such as outside research papers or whitepapers, can be removed from the incoming set after inventory when they do not need to remain as provenance or comparison evidence.

Next actions:

  • Keep using the project lineage pages for CICP, SCT, and POLEMEMELOP as the stable branch map.
  • Add only genuinely new intake here.
  • Exclude obvious personal material and clearly non-original third-party documents unless they are needed for provenance or review context.
  • Review the archived snapshot only if you need to inspect lineage history.
  • Move only the files that are clearly understood enough to justify it.
  • Continue pruning exact incoming clones only when a surviving copy already exists elsewhere.
  • Treat ipol_package as a separate ancillary bundle until its role is clearer.