Reference¶
Find a concept, inspect its exact definition, then follow the configured evidence. Qualified identities distinguish definitions with the same spelling in different modules or scopes.
Teaching contracts¶
The three instructional packages are deliberately small. Start here when learning notation or one boundary:
Question |
Entry |
|---|---|
How is a final nonnegative cost calculated? |
|
What distinguishes zero payment, decline and pending completion? |
|
Does an old target follow a fresh occurrence? |
|
Which actor and exact caller receive a completed return? |
These models have their own source and bounds. Their A/B labels and simplified records are not automatic aliases for the larger profile’s roles or state.
Reference-profile contracts¶
Meet the reference profile introduces its SideA/SideB roles and supplier boundaries. The entries below describe the full selected profile rather than substituting the teaching examples for it.
Contract |
Entry |
|---|---|
Components, supplied payment candidates and commitment |
|
Metadata values, name references and effective characteristics |
|
Locations, object renewal, ordered piles and observation |
|
Turn opportunities, objective procedures and ending boundaries |
|
Operation admission, instruction parts and completion |
|
Traversal, site selection, item inspection and return |
|
Ability definitions, instances, use, priority and caller return |
|
Information, conversion and supplied loop witnesses |
|
Current entries, activity epochs, pending and detached authority |
|
Owed work, cleanup, reactions and matched returns |
|
Neutral vocabulary and synthetic example/source contexts |
A source listing does not prove that every branch was exercised. A guard that consumes a supplier’s decision does not implement that supplier. Continue through Evidence before transferring a result to another configuration or implementation.
Modules¶
These pages are generated from the exact prepared neutral source. Every selected contract and frozen nested helper has its own entry. Additional local fixture helpers can remain within their owning definitions and complete downloads; each affected module explains its index scope.
- IdentityMC
- ObjectIdentity
- AtomicPayment
- CostAlgebra
- CostAlgebraMC
- PaymentWitnessMC
- PriorityMC
- PriorityProtocol
- AbilityChecksMC
- AbilityContracts
- AbilityProceduresMC
- AbilityRegistry
- ActionAdapters
- ActionCompositionMC
- ActivityChecksMC
- ActivityPublication
- AdditionalChecksMC
- AdditionalContracts
- AdditionalProceduresMC
- BasicContracts
- CommitmentProbesMC
- CommitmentPublicationMC
- CommittedCompositionMC
- CompletionOrderChecksMC
- CompositionOracle
- ConnectedTimingMC
- ConnectionFacts
- ControlChecksMC
- CostClampVariantMC
- DefinitionChecksMC
- DetachedChecksMC
- HostingChecksMC
- IdentityRenewalVariantMC
- InspectionChecksMC
- InspectionContracts
- InspectionProceduresMC
- InspectionTimingMC
- InterruptConditionVariantMC
- ItemTimingMC
- LocationChecksMC
- LocationContracts
- ObjectRuntime
- ObjectiveChecksMC
- OperationAdmissionVariantMC
- OperationChecksMC
- OperationContracts
- OperationProceduresMC
- PendingChecksMC
- PersistentChecksMC
- RegistryAvailabilityMC
- RegistryChecksMC
- RegistryCompositionMC
- RegistryUniquenessVariantMC
- RetirementChecksMC
- RuntimeChecksMC
- SchedulerChecksMC
- SchedulerOracle
- SchemaChecksMC
- SchemaContracts
- SettlementFacts
- SetupChecksMC
- SetupContracts
- SpecimenFactsA
- SpecimenFactsB
- TargetChecksMC
- TraversalChecksMC
- TraversalContracts
- TraversalIdentityVariantMC
- TraversalProceduresMC
- TraversalTimingMC
- TurnChecksMC
- TurnContracts
- TurnHandoffVariantMC
- TurnProceduresMC
- TypeChecksMC
- TypeContracts
- TypeOwnershipVariantMC
- UnitChecksMC
- VisibilityChecksMC