Uses of Package
ai.badmonkey.agentspaces.constraints
Packages that use 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.
-
Classes in ai.badmonkey.agentspaces.constraints used by ai.badmonkey.agentspaces.agentClassDescriptionThe gate (ISSUE-Constraints §9.4, FR-7 to FR-11): loads the newest complete version per book from the
constraintsspace (aVocabularyand everyConstraintcarrying 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. -
Classes in ai.badmonkey.agentspaces.constraints used by ai.badmonkey.agentspaces.constraintsClassDescriptionA 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
aandb(wire or simple names) narrowed by guards (field filter clauses), withnfor cardinality,within(an ISO duration) for response, thekey(field:<name>ortag:<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 theconstraintsspace (aVocabularyand everyConstraintcarrying 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:conditionsmaps a condition id to its text in the grammar ofConditionGrammar. -
Classes in ai.badmonkey.agentspaces.constraints used by ai.badmonkey.agentspaces.plannerClassDescriptionOne 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.
-
Classes in ai.badmonkey.agentspaces.constraints used by ai.badmonkey.agentspaces.springClassDescriptionThe gate (ISSUE-Constraints §9.4, FR-7 to FR-11): loads the newest complete version per book from the
constraintsspace (aVocabularyand everyConstraintcarrying 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.