Expand description
Cross-runtime contracts for GitNexus-style repo intelligence and impact-first AINL flows.
Crate has no openfang_* dependencies so it can ship stand-alone or with AI_Native_Lang tooling.
Re-exports§
pub use assertion::Assertion;pub use assertion::AssertionId;pub use assertion::AssertionState;pub use feature::Feature;pub use feature::FeatureId;pub use feature::FeatureSnapshot;pub use feature::FeatureStatus;pub use feature::VerificationStep;pub use handoff::Deviation;pub use handoff::DiscoveredIssue;pub use handoff::Handoff;pub use handoff::HandoffTests;pub use handoff::HandoffVerification;pub use handoff::InteractiveCheck;pub use handoff::IssueSeverity;pub use handoff::SkillFeedback;pub use handoff::TestAdded;pub use handoff::TestCase;pub use handoff::VerificationCommand;pub use mission::Mission;pub use mission::MissionCapabilityFlags;pub use mission::MissionId;pub use mission::MissionState;pub use mission_event::MissionEvent;pub use visibility::Visibility;pub use learner::FailureKind;pub use learner::ProposalEnvelope;pub use learner::TrajectoryOutcome;pub use learner::TrajectoryStep;pub use procedure::ExperienceBundle;pub use procedure::ExperienceEvent;pub use procedure::ProcedureArtifact;pub use procedure::ProcedureArtifactFormat;pub use procedure::ProcedureExecutionPlan;pub use procedure::ProcedureExecutionStep;pub use procedure::ProcedureLifecycle;pub use procedure::ProcedurePatch;pub use procedure::ProcedureReuseOutcome;pub use procedure::ProcedureStep;pub use procedure::ProcedureStepKind;pub use procedure::ProcedureVerification;pub use vitals::CognitivePhase;pub use vitals::CognitiveVitals;pub use vitals::VitalsGate;
Modules§
- assertion
- Validation assertions tied to mission milestones.
- context_
compiler - Context-compiler shared vocabulary (Phase 6 of SELF_LEARNING_INTEGRATION_MAP §15.1).
- feature
- Feature nodes within a mission DAG.
- handoff
- Structured worker handoff contract.
- learner
- Shared learner payloads (trajectory steps, failure taxonomy, proposal envelopes).
- mission
- Mission control-plane types (graph-native mission substrate).
- mission_
event - Mission progress events for SSE / audit streams.
- procedure
- Portable procedure-learning contracts.
- telemetry
- Telemetry / metrics field names — keep identical across ArmaraOS, AINL MCP, and optional inference-server.
- visibility
- Message visibility tiers for LLM vs user transcript filtering.
- vitals
- Cognitive vitals — structured signal derived from LLM token-level logprobs.
Structs§
- Recommended
Next Tools - Ordered recommendation list (validate → compile → impact/diff → run).
- Recommended
Tool Step - One recommended tool step in the impact-first chain (AINL MCP names or logical ids).
- Repo
Intel Capability Profile - Profile returned by
ainl_repo_intelnormalization.
Enums§
- Context
Freshness - Freshness of code/repo context for safe edits (independent of inference-server).
- Impact
Decision - Decision gate for executing versus gathering more context.
- Repo
Intel Capability State - Aggregate readiness for repo-intelligence MCP capabilities.
- Repo
Intel Tool Class - Class of repo-intelligence MCP tool (GitNexus-class naming).
Constants§
- CONTRACT_
SCHEMA_ VERSION - Version for JSON serialization of policy contract payloads (bump on breaking enum changes).
- LEARNER_
SCHEMA_ VERSION - Schema version for
ProposalEnvelopeand other learner wire types.