/** The six artifact verdicts. A verdict is always about a named subject, and this is the
 *  set for the subject "an authority artifact at a moment".
 *
 *  - `valid`             the verifier establishes the artifact currently confers the
 *                        authority claimed.
 *  - `invalid`           the verifier establishes it does not, or no longer does. Revoked,
 *                        expired, exhausted, void from issuance and dependent on an
 *                        invalid ancestor all land here, separated by reason code.
 *  - `not_established`   the verifier cannot reach a conclusion. Ignorance, never a
 *                        finding about the world, and never the negation of the claim.
 *                        See `EstablishmentGap` and `resolveEstablishedNegative`.
 *  - `not_yet_effective` the verifier establishes the artifact is validly issued and that
 *                        an enabling condition (a date, an event, an activation
 *                        attestation) has not occurred yet. The remedy is to wait, not to
 *                        find a better source.
 *  - `suspended`         use is paused by one or more live causes, each separately
 *                        releasable.
 *  - `restricted`        authority continues in reduced form under a live constraint that
 *                        does not pause it.
 *
 *  Concept source: aeoess/agent-authority-lifecycle, invariant candidates v2 section 2.2,
 *  and invariant L8 (suspension is not revocation). Proposed. */
export declare const LIFECYCLE_VERDICTS: readonly ['valid', 'invalid', 'not_established', 'not_yet_effective', 'suspended', 'restricted'];
export type LifecycleVerdict = (typeof LIFECYCLE_VERDICTS)[number];
/** What an enforcement point decides about ONE action at ONE authorization boundary.
 *  A different subject from `LifecycleVerdict`, kept apart on purpose: a composition rule
 *  that is not satisfied does not make any artifact invalid, it makes the action
 *  unauthorized at that boundary, and a restriction imposed from outside the chain denies
 *  the action without making the chain invalid.
 *
 *  Concept source: aeoess/agent-authority-lifecycle, invariant candidates v2 section 2.1.
 *  Proposed. */
export declare const BOUNDARY_OUTCOMES: readonly ['authorized', 'denied', 'not_established'];
export type BoundaryOutcome = (typeof BOUNDARY_OUTCOMES)[number];
/** Which limb was missing when a state could not be established. A `not_established`
 *  verdict that does not say which of the three was missing is unreadable, so this module
 *  makes at least one member mandatory on that verdict.
 *
 *  - `source`     no source the authority model accepts for this state produced a usable
 *                 answer, or the answer came from a source the model does not accept for
 *                 it, or two accepted sources are in unresolved conflict.
 *  - `freshness`  an answer existed but was older than the bound the model declares for
 *                 its source. Bounds are model declared, and this module declares none.
 *  - `coverage`   the claim does not state that it covers what the verdict needed. A
 *                 verifier must not read a state claim as covering more than it states.
 *
 *  Concept source: aeoess/agent-authority-lifecycle, invariant candidate BROAD-L7.
 *  Proposed. */
export declare const ESTABLISHMENT_GAPS: readonly ['source', 'freshness', 'coverage'];
export type EstablishmentGap = (typeof ESTABLISHMENT_GAPS)[number];
/** THE TWO MEANINGS OF "NOT ESTABLISHED", SPLIT.
 *
 *  Use A, the evidential sense, keeps the name. The verifier cannot reach the conclusion.
 *  That is `LifecycleVerdict` member `not_established`, and this module requires it to
 *  carry at least one `EstablishmentGap`, because saying which limb was missing is the
 *  whole content of the answer.
 *
 *  Use B, the established negative, is a conclusion the verifier HAS reached, and the
 *  conclusion is negative. Three shapes appear and none of them is `not_established`:
 *
 *  | shape                              | correct output                                 |
 *  |------------------------------------|------------------------------------------------|
 *  | enabling_condition_not_yet_occurred| artifact verdict `not_yet_effective`           |
 *  | composition_not_satisfied          | boundary outcome `denied`, stated reason       |
 *  | pinned_referent_mismatch           | boundary outcome `denied`, stated reason       |
 *
 *  Use `resolveEstablishedNegative` to get the right output for a shape rather than
 *  reaching for `not_established`. A module that reports ignorance for a positively
 *  established negative teaches the collapse this split exists to prevent.
 *
 *  Concept source: aeoess/agent-authority-lifecycle, invariant candidates v2 section 3.
 *  Proposed. */
export declare const ESTABLISHED_NEGATIVE_SHAPES: readonly ['enabling_condition_not_yet_occurred', 'composition_not_satisfied', 'pinned_referent_mismatch'];
export type EstablishedNegativeShape = (typeof ESTABLISHED_NEGATIVE_SHAPES)[number];
/** Resolution of one established-negative shape to its correct subject and output.
 *  Discriminated on `subject`: an artifact resolution carries `verdict`, a boundary
 *  resolution carries `outcome`. Neither ever carries `not_established`. */
export type EstablishedNegativeResolution = {
    readonly shape: 'enabling_condition_not_yet_occurred';
    readonly subject: 'artifact';
    readonly verdict: 'not_yet_effective';
    readonly reason_code: 'ENABLING_CONDITION_NOT_YET_OCCURRED';
} | {
    readonly shape: 'composition_not_satisfied';
    readonly subject: 'boundary';
    readonly outcome: 'denied';
    readonly reason_code: 'COMPOSITION_NOT_SATISFIED';
} | {
    readonly shape: 'pinned_referent_mismatch';
    readonly subject: 'boundary';
    readonly outcome: 'denied';
    readonly reason_code: 'PINNED_REFERENT_MISMATCH';
};
/** One cause, bound or condition still outstanding against an artifact.
 *
 *  Never a count and never a boolean. Causes compose: an artifact can be subject to more
 *  than one concurrent suspension or restriction cause, releasing one does not release
 *  another, and a verdict has to say which ones remain. `id` names the cause, `kind` says
 *  what sort of thing it is (this module does not enumerate kinds, the module that owns
 *  the cause does), `reason_code` is that module's stable code for it.
 *
 *  Concept source: aeoess/agent-authority-lifecycle, invariant candidate CAND-05.
 *  Proposed. */
export interface OutstandingCause {
    readonly id: string;
    readonly kind: string;
    readonly reason_code: string;
}
/** What a lifecycle module concludes about one artifact at one moment.
 *
 *  Reported ALONGSIDE a chain result, never merged into it. See `CompositeAuthorityResult`.
 *
 *  There is deliberately NO `valid` boolean on this type. `AuthorityValidationResult` has
 *  one and it is correct there, because that state set is genuinely two sided. Here the
 *  whole point is that `not_established` is not a boolean's false branch, and a truthiness
 *  shortcut invites exactly the collapse this vocabulary exists to prevent.
 *
 *  Construct with `lifecycleState` or `notEstablished`, which enforce the shape rules.
 *  Proposed. */
export interface LifecycleStateResult {
    readonly verdict: LifecycleVerdict;
    /** Stable, module-local, SCREAMING_SNAKE_CASE. Required on every verdict: two findings
     *  that share a verdict name must carry different reason codes, or a conformance claim
     *  that reports only verdict names is unreadable. This module defines the codes its own
     *  mapping produces (`LIFECYCLE_BASE_REASON_CODES`) and accepts any other module's. */
    readonly reason_code: string;
    /** Present with at least one member exactly when `verdict` is `not_established`. */
    readonly missing?: readonly EstablishmentGap[];
    /** Set when the authority model declared a default for absence and the verifier used it,
     *  which is how a verifier reaches a conclusion where it would otherwise have none.
     *  Incompatible with `not_established` by construction: if a default applied, the state
     *  was established. */
    readonly applied_default?: string;
    /** Present with at least one member exactly when `verdict` is `suspended` or
     *  `restricted`. Every cause still outstanding, as a set. */
    readonly outstanding?: readonly OutstandingCause[];
}
/** What a caller reports when a lifecycle module ran alongside chain verification.
 *
 *  `chain` is the draft-03 four-value result, byte for byte what
 *  `verifyAuthorityDelegationChain` returned. `lifecycle` is this vocabulary's answer,
 *  absent when no module ran. The two are never merged and the second never rewrites the
 *  first: a later finding is a new record that references an earlier one. */
export interface CompositeAuthorityResult<TChain> {
    readonly chain: TChain;
    readonly lifecycle?: LifecycleStateResult;
}
/** The reason codes this module's own mapping emits. Other lifecycle modules mint their
 *  own. `reason_code` is typed as `string` so they can, and this list is not a closed
 *  universe. Named here so the mapping's codes do not drift silently. */
export declare const LIFECYCLE_BASE_REASON_CODES: readonly [
/** valid: chain verification returned valid and nothing else was asked. */
'CHAIN_VALID', 
/** invalid: the chain result carried no failure to name. */
'CHAIN_INVALID', 
/** not_established: chain verification returned unsupported and named no code. */
'CHAIN_UNSUPPORTED', 
/** not_established: chain verification returned indeterminate and named no code. */
'CHAIN_INDETERMINATE', 
/** not_yet_effective: the time facet's not_before has not been reached. */
'NOT_BEFORE_UNREACHED'];
export type LifecycleBaseReasonCode = (typeof LIFECYCLE_BASE_REASON_CODES)[number];
//# sourceMappingURL=types.d.ts.map