A Atlantis Core

Reference

Contract Reference

A compact reference for the main AtlantisV2 core objects implemented so far.

# AtlantisV2 core pipeline
ReferenceTime
  -> MarketSnapshot
  -> FeatureVector
  -> PatternHit[]
  -> TradeHypothesis
  -> SignalIntent
  -> PermissionDecision
  -> PositionIntent
  -> OutcomeRecord

This page summarizes the implemented core contracts. It is not a full API reference. It is a map of object responsibility and boundary ownership.

Time

ContractRole
ReferenceTimeAs-of timestamp for decisions
ClockProtocol for explicit time source
FixedClockDeterministic clock for tests and replay
CycleContextIdentity and time context for one evaluation cycle
FreshnessPolicyMax-age check for event freshness
SessionContextSession and tradability metadata

Market

ContractRole
EventEnvelopeAdapter-normalized input event
EventLineageSource event lineage retained after normalization
MarketEventCore market event after envelope normalization
MarketSnapshotCapability-bearing market state
UnderlyingRefUnderlying identity
InstrumentRefInstrument identity
PriceCapabilityPrice availability and value
VolumeCapabilityVolume availability and value
SnapshotQualitySnapshot quality flags

Adapters

ContractRole
AdapterEventBatchValidated event batch crossing into Core
MarketDataAdapterProtocol for market payload normalization
ExpressionAdapterProtocol for intent expression
ExpressionRouterRoutes preferred exposure to compatible adapter
AdapterAttributionAdapter id, version, and metadata on expressions

Features And Patterns

ContractRole
FeatureDefinitionFeature metadata and required capabilities
FeatureRegistryImmutable registry of definitions
FeatureVectorComputed features and availability
FeatureProvenanceFeature source and calculation metadata
PatternDefinitionPattern metadata, stages, hash, requirements
PatternRegistryImmutable pattern registry
PatternHitEvidence-rich pattern match
PatternAvailabilityEligible, stale, retired, cooldown, disabled states

Scoring And Intent

ContractRole
TradeHypothesisScored thesis from pattern evidence
EvidenceStackPattern hits contributing to a hypothesis
ConvictionBreakdownScoring dimensions and final score
SignalIntentInstrument-neutral thesis handoff
ExposurePreferenceDesired expression family
InvalidationContextPortable invalidation information
TargetContextPortable target information
IntentConstraintsConstraints carried into permission/expression
EvidenceSummaryCompact attribution summary

Permission

ContractRole
RiskContextInputs to permission evaluation
PermissionDecisionAllow, reject, defer, or downgrade result
PermissionStatusPermission taxonomy
ReasonCodeStable permission reason enum
ConstraintResultApplied permission constraint
OperatorSwitchesKill switch and operator controls
PortfolioLimitsPortfolio-level risk controls

Lifecycle And Outcomes

ContractRole
PositionIntentAdmitted thesis ready for expression
ExpressionRequestPreferred exposure and constraints
ExposureExpressionAdapter-selected exposure candidate
ExpressionResultExpressed, rejected, pending, or failed result
OpenExposureTracked open exposure
LifecycleTransitionAppend-only state change record
MarkEventIncoming mark observation
MarkRecordPersistable mark observation
CloseEventIncoming close observation
OutcomeRecordClosed outcome with path and economic labels

Boundary Summary

Core contracts should be portable across:

  • live
  • paper
  • shadow
  • replay
  • backtest
  • research

If a field only makes sense for one broker, one venue, one database table, or one dashboard, it probably does not belong in these contracts.