01
Capture
Records enter under controlled custody with their origin, version and hash intact.
Buyer
Counterparty qualification, specifications and controlled purchase decisions.
A category describes what you do, not what you hold. Selecting it asserts nothing about any licence, registration or accreditation.
Specific to this category
What differs for a buyer.
—
Evidence this category ownsCounterparty qualification and audit, incoming specifications, evidence acceptance criteria, disclosed exceptions.
—
Where it hands offSees only what each counterparty has explicitly granted. This is not a marketplace and there is no open directory.
—
State-overlay sensitivityLow directly; inherits the sensitivity of whoever it buys from.
—
Applicable document familiesThe shared core plus the sourcing set: counterparty qualification and audit, incoming specifications and acceptance criteria, evidence review and exception handling, approved supplier maintenance, and disqualification and re-qualification.
—
Typical counterparty grantsAlmost purely a recipient, and only of what each counterparty has explicitly granted. There is no directory, no open discovery and no marketplace matching. What a buyer grants outward is its own qualification requirements and specifications, nothing more.
Same for every category
What the platform does, for every category
No authority transmission. FederalCompliance does not file, submit or transmit anything to FDA, DEA, a state authority or any other body.
02
Screen
Deterministic checks run against the configured rule pack. Model output is candidate wording only.
03
Tidy
Gaps, conflicts and missing evidence are surfaced rather than filled in.
04
Review
An accountable person decides. The platform never decides.
05
Approve
A frozen, source-linked package is created with an exact manifest.
06
Download
The customer downloads and submits through their own authorized channel.
Order of precedence
The applicability stack, in this order
Every rule version records authority, citation, source version and hash, effective date, applicability condition, reviewer, confidence and supersession. A state overlay stays NOT_CONFIGURED until its primary-source pack passes qualified review.
01
Federal statute and current regulations
02
DEA registration and activity rules
03
FDA product, development and quality rules, when applicable
04
State statute, regulation, licence conditions and official guidance
05
Local fire, building, security and business requirements
06
Customer quality agreements, specifications and SOPs
07
System-integrity rules
The shared rail
The record every category writes into
Events
Inventory, custody, transformation and disposition, each attributable and timestamped.
Claims
Falsifiable statements with provenance, confidence and supersession.
Signatures
Who decided what, when, against which exact bytes.
Evidence objects
Versioned source material under one of four custody modes.
Export packages
Frozen manifests, reviewed and approved before download.
Access
Getting in
Not a trial and not a demo. The open house creates no evidence, so nothing has to be honoured or unwound later.
01
Open houseSign up, confirm your email, and read. Your workspace and the regulatory catalog are open immediately. Nothing is recorded, because nothing is writable yet.
02
ApprovedOrganization review completes. You may now activate a subscription.
03
ActiveEvidence entry, counterparty sharing, review packages and downloads switch on.
Boundaries
What is never claimed, for any category
—
FDA approval, DEA registration and state licensure are three separate status objects. No interface combines them into a generic "federally compliant" badge.
—
Selecting a category asserts nothing about whether an organization holds, or is eligible for, any licence, registration, accreditation or quality status.
—
Adult-use operating records may be preserved as starting evidence for a transition assessment. They are never silently relabelled as medical, federal or GMP records.
—
Model output is candidate extraction or suggested wording. It is never authority, and it is never described as verification.
Buyer
Start with the federal baseline. Activate the state you operate in.
No state rule is treated as configured until its primary sources, effective dates and reviewer approval are recorded.