/capabilities
yawn.bot

Capabilities

yawn.bot/capabilities
/

Participant information is not included in this view.

    No purpose vector foundChat
    1. What can this actor actually do here—and under which conditions?

      A capability is a bounded ability. It becomes usable only when access, authority, resources, availability, and proof all line up.

      Why is this question here?

      Source order · no numerical ranking receipt supplied

      This view preserves the order supplied by its source adapter. Its position is not a probability or a measure of truth.

      How is this answer supported?
      How YAWN holds it

      Capabilities

      This coordinate keeps ability separate from permission. A principal's current grant count belongs in an authenticated Agent-Space aperture; it is never a claim about universal powers.

      1. Ability

        The operation the actor or system can perform.

      2. Access

        The tools, data, relationships, or interfaces it can currently reach.

      3. Authority

        Who has permitted the operation, within which boundary.

      4. Availability

        Whether the dependency is working in this moment.

      5. Proof

        The witness that the operation worked as claimed.

      Which capability types does this bot expose?
      • agent_space.owneragent_space · @dave · owner-scope

        Own the root Agent Space; every other owner grant hangs from this membership.

      • yawn.readyawn · @dave · owner-scope

        Read canonical Yawns, materialized states, and receipts inside the owner's Agent Space.

      • yawn.proposeyawn · @dave · owner-scope

        Open a change proposal against a Yawn. A proposal is not a decision.

      • yawn.decideyawn · @dave · owner-scope

        Accept or reject a proposal as the rightful owner.

      • proof.recordproof · @dave · owner-scope

        Record a proof receipt: prediction, verifier, falsifier, status.

      • budget.requestbudget · @dave · budget-capped

        Request a run budget under the $50 monthly cap; $0 autonomous paid work; approval required.

      • connector.github.readconnector.github · @dave · owner-scope

        Read repositories, pull requests, and checks through the GitHub connector.

      • connector.github.writeconnector.github · @dave · explicit-owner-authorization

        Write to GitHub only with explicit owner authorization and a proof requirement; no paid model calls.

      • deployment.publishdeployment · @dave · explicit-owner-authorization

        Publish a deployment only with explicit owner authorization and a proof requirement.

      • connector.github.inspectconnector.github · @yawn · execution-delegate

        Inspect a pull request for the owner's control plane; exact effect signature required.

      • connector.github.prepareconnector.github · @yawn · execution-delegate

        Prepare a bounded work order against an inspected pull request; nothing executes yet.

      • connector.github.execute_work_orderconnector.github · @yawn · execution-delegate

        Execute an active work order whose exact effect signature matches; a stale SHA suspends the match.

      • action.policy.matchaction.policy · @yawn · execution-delegate

        Match an observed action against an active policy; proof required, $0 cost.

      • action.policy.proposeaction.policy · @yawn · execution-delegate

        Propose an action policy for the owner to decide. Proposing grants nothing.

      • action.receipt.recordaction.receipt · @yawn · execution-delegate

        Record an action receipt after an executed effect so the consequence is inspectable.

      Types are not grants. A principal's active grants live in its own aperture: yawn.bot/dave/capabilities

      What does this model leave unclaimed?
      • A capability is not permission.
      • A grant is not proof that the capability is currently available.
      • A capability count is not a score of intelligence, agency, or human worth.
      • Inherited language does not silently inherit private data or authority.
      Source and projection status

      Application-governed public View. It does not claim a corresponding canonical Supabase Yawn, Event, or Proof Receipt.

      Governing protocol lock: yawn-ai/.yawn@82804ade6292fa5d1150e578b72c4a4686662e6b

      Consulted upstream specification witness (not promoted): yawn-ai/.yawn@f71374940c5c192c89d81136d36ec5f448a0b0ec

      • Governing source: core/holarchy.yawn
      • Governing source: schemas/agency-holarchy.v0.2.schema.json
      • Specification witness: spec/ontology.md
      • Specification witness: core/proof-and-boundary.yawn
      • Specification witness: core/projection-and-aperture.yawn
      OntologyAgentic efficiencyCodex
    2. When should one capability become several narrower grants?

      Working answer

      Split it when recipients, effects, revocation, or proof requirements differ.

      Why is this question here?

      Source order · no numerical ranking receipt supplied

      This view preserves the order supplied by its source adapter. Its position is not a probability or a measure of truth.

    3. Does a configured connector prove a capability is available?

      Supported

      No. Configuration is evidence of possible access; a current bounded check proves availability.

      Why is this question here?

      Source order · no numerical ranking receipt supplied

      This view preserves the order supplied by its source adapter. Its position is not a probability or a measure of truth.

    4. Can confidence create authority?

      Supported

      No. Confidence can rank a proposal; only the rightful principal can grant authority.

      Why is this question here?

      Source order · no numerical ranking receipt supplied

      This view preserves the order supplied by its source adapter. Its position is not a probability or a measure of truth.