What qualifies as a FilingSift covenant event
A covenant event requires an identified obligation or threshold, exact source evidence, an accession and source URL, and a defensible relationship to the previous comparable disclosure. Keyword presence alone is not a covenant event.
Supported event shapes
The extraction contract can represent additions, removals, and threshold changes; leverage and coverage tests; minimum-liquidity requirements; waivers; breaches; amendments; and forbearance language. A change record must distinguish the obligation, metric, comparator, threshold, effective context, and evidence.
Noise controls
FilingSift suppresses harmless date roll-forwards, formatting changes, and equivalent wording when standardized evidence supports equivalence. It refuses a comparison when a covenant cannot be matched reliably across filings. It does not infer compliance, default, materiality, or severity from a keyword match.
Current coverage
The current AAPL public records contain zero extracted legal or financing signals, so FilingSift does not generate an indexable AAPL covenant-event page. This methodology page is published to define the gate; issuer pages appear only when a real, evidence-backed event exists.
Review requirement
Even a machine-checked covenant change is a structured research lead, not legal advice. Review the complete cited agreement, amendment, filing context, definitions, baskets, exceptions, and effective dates before drawing a conclusion.
Content snapshot: . Current API data may be newer.