Uses of Package
ai.badmonkey.agentspaces.constraints

Package
Description
The framework-neutral agent binder: annotated plain objects become fleet workers with automatic AgentCards (plan §10.3).
Rule entries and the constraint gate (ISSUE-Constraints): the reserved entries, the condition grammar, the marking engine for the four templates, and the gate the binder consults before a claim and a result write.
The planner (ISSUE-CardContract, SPEC §6.1b): the Planner SPI over PlanActions read from agent cards and PlanningStates read from a key's events and marking; the enablement and search planners; a plan as PlannedSteps a peer writes as PlanStep entries workers take.
Spring Boot autoconfiguration for AgentSpaces (spec §10.1): properties-driven peer, group, and space wiring behind the fluent facade, with lifecycle-driven ticking and annotation-driven bean enrollment.
  • Class
    Description
    The gate (ISSUE-Constraints §9.4, FR-7 to FR-11): loads the newest complete version per book from the constraints space (a Vocabulary and every Constraint carrying its hash, from an issuer the authorizer permits to write the scope), keeps one key's events from the lanes it watches (seeded from what the replica holds, then from each lane's notifications, so a take it cannot read back still counts; a lane is read again when a version or an interest names a new type), and answers two questions: may this entry be claimed, and may this result be written.
  • Class
    Description
    A parsed condition, evaluated over one key's events at a moment.
    One unit of a published version (ISSUE-Constraints FR-2, FR-4): a template over the types a and b (wire or simple names) narrowed by guards (field filter clauses), with n for cardinality, within (an ISO duration) for response, the key (field:<name> or tag:<name>) that groups entries, and the enforcement list (gate, monitor, jury, approval, planner).
    The gate (ISSUE-Constraints §9.4, FR-7 to FR-11): loads the newest complete version per book from the constraints space (a Vocabulary and every Constraint carrying its hash, from an issuer the authorizer permits to write the scope), keeps one key's events from the lanes it watches (seeded from what the replica holds, then from each lane's notifications, so a take it cannot read back still counts; a lane is read again when a version or an interest names a new type), and answers two questions: may this entry be claimed, and may this result be written.
    The gate's answer.
    One event of a key in issue order (FR-6): the entry's simple and wire type, its id, when it was issued, its fields (a record's components or a map's entries), its tags, and whether it is a write or a claim.
     
    The marking of one key under one version (§9.3): the state per unit, the types the constraints enable next, the types they refuse, the units awaiting a jury, and the violations the events already show.
    A unit's refusal or observed violation on the key.
    One loaded version: its vocabulary and the constraints that carry its hash (FR-7).
    One version's named conditions (ISSUE-Constraints FR-2), the situations a book's sentences name: conditions maps a condition id to its text in the grammar of ConditionGrammar.
  • Class
    Description
    One event of a key in issue order (FR-6): the entry's simple and wire type, its id, when it was issued, its fields (a record's components or a map's entries), its tags, and whether it is a write or a claim.
    The marking of one key under one version (§9.3): the state per unit, the types the constraints enable next, the types they refuse, the units awaiting a jury, and the violations the events already show.
  • Class
    Description
    The gate (ISSUE-Constraints §9.4, FR-7 to FR-11): loads the newest complete version per book from the constraints space (a Vocabulary and every Constraint carrying its hash, from an issuer the authorizer permits to write the scope), keeps one key's events from the lanes it watches (seeded from what the replica holds, then from each lane's notifications, so a take it cannot read back still counts; a lane is read again when a version or an interest names a new type), and answers two questions: may this entry be claimed, and may this result be written.