Struct AgenticSystem

Source

pub struct AgenticSystem { /* private fields */ }

Expand description

One revision of one agentic system design.

Implementations§

Source §

impl AgenticSystem

Source

pub fn draft( id: AgenticSystemId, purpose: SystemPurpose, integrator: SystemRoleId, roles: impl IntoIterator<Item = SystemRole>, participants: impl IntoIterator<Item = LogicalParticipant>, topology: impl IntoIterator<Item = CollaborationLink>, profiles: impl IntoIterator<Item = (SystemRoleId, RequestedExecutionProfile)>, ceremonies: impl IntoIterator<Item = CeremonyComposition>, supervision: SupervisionPolicy, attention: AttentionPolicy, now: OffsetDateTime, ) -> Result<Self, DomainError>

Start a design at its first revision.

Deliberately permissive about the content: a draft is something an author is still working on, and refusing to write down a half-finished system would mean the only way to get advice about one is to have finished it. What is refused here is what no revision of the design could ever repair — an empty system, or one whose own indexes disagree with themselves.

Source

pub const fn integrator(&self) -> &SystemRoleId

The business role that drives the system from outside it.

Source

pub const fn roles(&self) -> &BTreeMap<SystemRoleId, SystemRole>

Source

pub const fn participants(&self) -> &BTreeMap<ParticipantId, LogicalParticipant>

Source

pub fn topology(&self) -> &[CollaborationLink]

Source

pub const fn profiles( &self, ) -> &BTreeMap<SystemRoleId, RequestedExecutionProfile>

Source

pub const fn ceremonies( &self, ) -> &BTreeMap<SystemCeremonyId, CeremonyComposition>

Source

pub const fn supervision(&self) -> &SupervisionPolicy

Source

pub const fn attention(&self) -> &AttentionPolicy

What the integrator asked to be told about while it runs.

Source

pub const fn created_at(&self) -> OffsetDateTime

Source

pub const fn updated_at(&self) -> OffsetDateTime

Source

pub fn digest(&self) -> Result<AgenticSystemDigest, DomainError>

The content identity of this design.

Source

pub fn pin(&self) -> Result<SystemPin, DomainError>

This design, named the way a run refers to it.

Source

pub fn edited(&self, now: OffsetDateTime) -> Self

The same design saved as the next revision.

Editing produces a new revision rather than mutating this one, because the store’s compare-and-swap is what protects one author’s edit from another’s, and it can only compare revisions it was told about.

Source

pub fn at_revision(&self, revision: AgenticSystemRevision) -> Self

The same design, recorded at a revision the store assigned.

Source

pub fn published(&self, now: OffsetDateTime) -> Result<Self, DomainError>

Seal this revision.

Refused from anything but a draft: publishing a published revision again would either be a no-op dressed as an event or a silent overwrite of something a run may already be pinned to.

Source

pub fn deprecated(&self, now: OffsetDateTime) -> Result<Self, DomainError>

Retire this revision from new runs without invalidating the ones already sealed against it.

Source

pub fn blocking_dependencies( &self, ) -> BTreeMap<SystemCeremonyId, Vec<SystemCeremonyId>>

What each composition must wait for before it can run.

Not simply depends_on: a bounded loop declares which edge is the way back round, and that edge is cut here so a system that sends work back for revision can start at all.

Source

pub fn root_ceremonies(&self) -> Vec<&CeremonyComposition>

The compositions nothing else has to finish first.

These are where a run begins. A design where every composition waits for another has a cycle nothing bounded, and the analysis says so before a run has to discover it by starting nothing.

Source §