NeatContext
Foundation active
Git-backed collaboration platform

Knowledge moves through review. Context stays close to the agent.

NeatContext adds a deliberate proposal and release path around local Contexts—without putting the platform in the grounding loop.

Open repository settingsExplore the lifecycleAPI health
One publication path

From local work to an exact release

Every release crosses the same human review and validation gates, regardless of its eventual audience.

  1. 01

    Propose

    An explicit plugin action sends one validated Context snapshot to the platform.

  2. 02

    Review

    The platform opens a scoped GitHub pull request. Repository policy stays in charge.

  3. 03

    Publish

    A merge becomes eligible only after exact-commit validation and an explicit publish action.

  4. 04

    Retrieve

    Authorized plugins receive a manifest and bounded files from the recorded commit.

Implementation progress

The secure platform channel is becoming code.

Git-backed publication, immutable retrieval, device authorization, and the first bounded plugin-facing routes now share one reviewed control-plane boundary.

Portable content contractImplemented with golden policy tests
Proposal lifecycleMerge cannot bypass explicit publication
Device authorization APIBounded routes, live revocation, and stable problems
Repository settings UIAccount-scoped verification, edits, and safe disconnects
Team organizationsOwner/admin teams with active-member assignments