wiki/projects/looptloop

Rendered from markdown source. Open raw source on GitHub.

LOOPtLOOP

This project collects the public witness and provenance surface around LOOPtLOOP.

It is the top-level project entry for the hash-only authorization, witness receipt, and live provenance loop family now exposed at looptloop.online.

Semantic Role

This project is the public contract surface for LOOPtLOOP. It is where the wiki treats hash-only authorization, bounded witness, and provenance loops as a real project rather than only a concept or historical artifact cluster.

The important distinction is that this page points at a live machine-readable public system, while the concept page explains the meaning of the term. The project page should stay oriented toward deployment, public contract, and supported lineage.

Current Shape

• 1 top-level project landing page.
• 1 public machine-readable surface.
• 3 legacy branches that now act as supporting lineage: CICP access, WitnessKey, and the archived patent companions.

Public Surface

• Public site
• Machine-readable summary
• API base
• Public repository

Core Claims

• Private payload stays private.
• Witness is bounded and hash-first.
• Consent envelopes and provenance signals can be public without exposing the underlying payload.
• The public surface is narrow on purpose and should not be inflated into a broader identity claim.

Mechanisms

• Hash locally before witness.
• Verify receipts and status explicitly before reliance.
• Use provenance loops for visible recording claims.
• Keep the public contract machine-readable so downstream tooling can consume it safely.

Implications

• The project can be entered from Projects without knowing the historical patent lineage first.
• The wiki can treat LOOPtLOOP as a current public project surface, not only a historical acronym.
• CICP, WitnessKey, and the patents branch remain supporting lineages rather than the primary entry point.

Primary Pages

• LOOPtLOOP
• Implementation and Access
• Pairing and Field Access
• Field Pairing and Consent Loop
• Field Infrastructure Applications
• WitnessKey
• Platform and Field Applications

Working Read

LOOPtLOOP is the project where hash-only witness, consent envelopes, and provenance loops become a public surface with a machine-readable contract.

The project now sits alongside the other top-level wiki projects, so readers can enter from Projects and then move down into the CICP, WitnessKey, or patents branches depending on whether they want access, authorization, or historical lineage.

The public contract is intentionally narrow: it witnesses hashes, preserves private payload boundaries, and makes provenance visible without claiming more than the API supports.

Dependencies

• LOOPtLOOP
• Witnessing
• Intent-Consent
• Governance Diad
• LoopLink
• Consent–Intent Compression Protocol (CICP)
• WitnessKey
• Platform and Field Applications

Open Questions

• How far should the public witness contract expand before it stops being LOOPtLOOP?
• Which provenance claims belong on the public surface versus in supporting lineages?
• When does a legacy companion become a separate project rather than an archived branch?

Related Concepts

• LOOPtLOOP
• Witnessing
• Intent-Consent
• Governance Diad
• LoopLink

Attractor Bridge

• Consent
• Witness
• Provenance
• Trust

Notes

• This is a project page, not a canon claim.
• Keep the public site, concept page, and supporting branches consistent with the same bounded witness contract.
• Treat looptloop.online as the live public surface for the project.