← Prompted LLC
    Canonical · Portable Governance Lifecycle·Proof of concept

    Context Grapple Gun

    Context Grapple Gun is a portable governance lifecycle for Claude Code and a developer-facing entry point into Prompted LLC's Ubiquity substrate. It captures lessons from real work, routes them through human review, promotes them through scoped gates, and hydrates approved guidance back into future sessions — without confusing rendered context with constitutional source of truth.

    The unified frame

    Prompted LLC builds Ubiquity so AI systems can know when to act, when to ask, and how to turn human judgment into safer autonomy over time.

    Context Grapple Gun, also published as the open-source context-grapple-gun repository (prompted365/context-grapple-gun), is the developer-facing implementation of this portable lifecycle.

    CGG applies the Ubiquity thesis locally: capture lessons from real work, route them through human review, promote them through scoped gates, and hydrate approved guidance back into future sessions — without confusing rendered context with constitutional source of truth.

    Lifecycle, not memory

    CGG is not about remembering more. It is about making reviewed judgment durable.

    capture → human review → scoped promotion → hydration

    Lessons from real development work — corrections, architectural decisions, edge cases, recurring mistakes — are captured as proposals. They route through human review. Approved lessons are promoted through scoped gates. Durable guidance is hydrated back into future sessions. The window does not grow. The judgment compounds.

    Cognitive pull requests

    A code pull request proposes a change to software.

    A cognitive pull request proposes a change to the working memory, guidance, or operating assumptions of an AI-assisted development system. It creates a reviewable seam before lessons silently harden into the system's behavior — and before reviewed lessons evaporate with the chat history.

    Governed memory vs. token bloat

    A bigger context window does not solve drift. Long histories can preserve more text while still losing operational meaning. CGG turns recurring lessons and corrections into reviewed guidance, so the system does not need to rediscover the same truths every session. See token bloat vs. governed memory for the contrast.

    The hybrid boundary

    CGG is complete without Ubiquity. It uses local, auditable, flat-file governance so teams can capture, review, promote, and hydrate lessons without standing up a full substrate.

    When flat-file governance is no longer enough, Ubiquity extends the same primitives into deeper substrate infrastructure: semantic recall, graph topology, conformation-aware retrieval, expression gating across timescales, endogenous economics, and compiled execution-boundary enforcement.

    CGG is the lifecycle. Ubiquity is the substrate that lifecycle seeds.

    Repository and install

    Canonical repository: github.com/prompted365/context-grapple-gun. The dashed form is the package and repository slug; the spaced form is the product name. References to "live healthcare deployments at scale," specific token thresholds, or system-prompt mutation are not canonical claims — defer to the repository and this page.

    Demand ladder

    L1 Pain→L2 Contrast→L3 Category→L4 Primitive→L5 Branded
    ← Up the funnel
    Claude Code context governance
    Down the funnel →
    AI governance research substrate

    This is

    • A portable governance lifecycle for Claude Code-style agentic development.
    • A developer-facing entry rung into Ubiquity's substrate grammar.
    • A cognitive-pull-request review surface for AI-assisted work.
    • Flat-file auditable: local, inspectable, version-controllable.
    • Substrate-seedable: the same primitives extend into Ubiquity when flat files run out.
    • Cross-session lesson compounding for long-running development work.

    This is not

    • The full Ubiquity substrate.
    • Merely a Claude Code memory tool.
    • A vector database.
    • A magical memory layer.
    • A hosted platform.
    • A PR-productivity dashboard.
    • A generic context manager.
    • A fictional grappling hook, Batman gadget, or Palworld item.
    • The npm grappling-hook / keystonejs package.

    Frequently asked

    Is Context Grapple Gun the same as `context-grapple-gun` on GitHub?
    Yes. Context Grapple Gun is the product name; `context-grapple-gun` is the dashed repository and package slug. The repository is github.com/prompted365/context-grapple-gun.
    Is CGG the Ubiquity substrate?
    No. CGG is complete without Ubiquity. It is the portable governance lifecycle that proves Ubiquity's grammar inside Claude Code. When flat-file governance is no longer enough, Ubiquity extends the same primitives into deeper substrate infrastructure.
    Is CGG just a Claude Code memory tool?
    No. Memory stores information. CGG governs how lessons become durable: capture, human review, scoped promotion, and hydration. The point is not a bigger window — it is reviewed judgment that compounds across sessions.
    Does CGG replace human judgment?
    No. CGG creates reviewable seams where human judgment decides what becomes durable guidance. The human is moved to the edge of earned trust, not removed from it.
    What is a cognitive pull request?
    A code pull request proposes a change to software. A cognitive pull request proposes a change to the working memory, guidance, or operating assumptions of an AI-assisted development system. CGG uses cognitive PRs as the reviewable seam before lessons become durable.

    Canonical references

    Root frame

    This surface sits inside Prompted LLC's governance substrate for sovereign adaptive systems. Sovereignty here is the continuity condition — agency that survives amplification — not sovereign cloud, data residency, or model hosting.