Document & review
workspace
Keep authorization evidence, dates, owners and unresolved review tasks in one place.
ROOTED IN MOROCCO. BUILT FOR CONNECTION.
Every batch.
One connected
story.
The operating layer for Morocco’s
legal cannabis supply chain.
A proposed private platform connecting operators, cooperatives, independent laboratories and buyers through evidence they can follow.
Platform vision & demonstration · Open interactive prototype
CONNECTED EVIDENCE / ILLUSTRATION
01 / SOURCERif Valley CooperativeOrigin & custody records
✓BATCH PASSPORTFICTIONAL DEMO
RIF-26-0847
One identity. A traceable history.
Source batchLinked
Independent lab evidenceLinked
Destination authorizationOpen item
HR
Human review stays in controlNo automatic export approval
02 / INDEPENDENT EVIDENCECOA-26-184Linked to sample SMP-26-184
03 / CONTROLLED SHARINGOne versioned buyer dossier →
ORIGINEVIDENCEREVIEW
THE WHY
Records exist.
The connection is missing.
A batch can cross several organizations. Its evidence often travels separately. RifTrace is designed to make that handover easier to follow and easier to review.
THE WORKFLOW TO IMPROVEAssembling a story,
Assembling a story,
one request at a time.
Separate files, unclear versions and repeated requests can leave teams asking: “Which batch? Which report? Who checked it?”
THE RIFTRACE APPROACHOne evidence trail.
One evidence trail.
Clear responsibility.
- 01Find the right record
Connect source lots, samples and reports to a shared batch identity.
- 02See what is still missing
Assign review tasks and keep expired, amended or unresolved evidence visible.
- 03Prepare once, share deliberately
Assemble a versioned dossier for a specific buyer and purpose.
These are workflow hypotheses to validate with operators. Software can organize evidence; it cannot make an inaccurate source record true.
THE WHO
Different roles.
Shared context.
Start with a processor or exporter workspace. Invite the people who contribute evidence or review a batch, with access limited to their role.
THE ANCHOR WORKSPACE
Less chasing.
More control.
Give operations and quality teams one place to assemble a batch dossier, assign missing items and prepare a controlled handover to a buyer.
- Link supplier documents, batches and laboratory reports.
- Track owners, expiry dates and review decisions.
- Reuse approved evidence in a versioned buyer pack.
VALUE TO MEASUREHours spent preparing each complete dossier.
✳
One anchor can connect a supply chain. Invited participants are not automatically paying customers. Each organization keeps its own responsibilities and controls what it shares.
THE HOW
Follow one batch.
See the difference.
From cooperative records to a buyer’s review desk, without losing the links in between.
FICTIONAL SCENARIO All organizations, records and events below are illustrative. No live shipment or customer data.
01 / RIF VALLEY COOPERATIVEGive the batch
Give the batch
an identity.
A cooperative registers source batch RIF-26-0847 and connects its origin documents and responsible operator. The record begins with a named source, not a detached PDF.
THE BENEFIT
Future records can refer to the same batch instead of recreating its identity.
01 / 05
SOURCE RECORDDEMO
RIF-26-0847
Rif Valley Cooperative
- Origin evidence
- Attached
- Responsible operator
- Assigned
- Batch identity
- Created
!
Source documents still require review. A record is not an authorization.
COA = certificate of analysis. Reports are issued by the independent laboratory. RifTrace links and preserves them; it does not perform testing, issue analytical certificates or approve exports.
THE WHAT
One operating layer.
Not another silo.
“OS” means a shared workflow across organizations. The first release should solve a complete evidence handover, before expanding into a wider industry platform.
Document & review
Batch
traceability
Link source lots, custody events, transformations and outputs with consistent identifiers.
Independent
lab evidence
Connect sample IDs, original reports, issuers and amendments without changing laboratory responsibility.
Buyer dossier
& handover
Prepare a versioned evidence index with named review and access limited to agreed recipients.
A shared, permissioned foundation
Common identifiers · Role-based access · Version history · Accountable review · Portable exports
INSIDE THE PLATFORM
Record, link, flag, review and share supporting evidence.
OUTSIDE THE PLATFORM
Cultivation, transformation, laboratory testing, official authorizations and transaction execution remain with the responsible organizations.
Explore the broader OS vision
Future modules are options, not delivery commitments. Add them only when customer demand, data quality, permissions and operating capability justify the work.
Trade coordination
Structured requirements and RFQs for verified counterparties, subject to legal scope.
Logistics visibility
Transport milestones and document handovers from authorized service providers.
Intelligence & executive views
Operational trends drawn from reliable, permissioned data.
AI assistance
Extract fields and flag gaps for human review, never issue regulatory decisions.
Finance interfaces
A separate future assessment of consent, fairness and financial regulation.
Institutional reporting
Only for authorized recipients and agreed data. No official relationship or integration is assumed.
THE CASE FOR RIFTRACE
Why it can work.
What must be proven.
A credible platform needs more than a compelling interface. The logic is practical; its commercial and operational results still have to be earned.
A documented need for evidence
Morocco’s legal framework defines activity-specific authorizations and record obligations. That creates a real documentation context, but not automatic demand for RifTrace.
Source: ANRAC investor guide →THE DESIGN RESPONSE
Support operator-side evidence and review without claiming to replace official records.
Prove it through legal scope review and actual customer workflows.A small starting point with daily value
One processor or exporter can use a complete batch dossier workflow without waiting for every participant in the country to adopt the platform.
Product and adoption hypothesisTHE DESIGN RESPONSE
Sell a focused workspace, include invited contributors and measure repeat use.
Prove it through paid pilots, retained use and collected subscription revenue.Quality depends on the evidence trail
Independent reports, source records and accountable review matter in regulated workflows. Applicable GACP and GMP guidance reinforces the importance of reliable documentation and controlled systems.
Source: EMA GACP guidance →THE DESIGN RESPONSE
Preserve originals, amendments and review history. Validate controls for the intended use.
Prove it through record audits, permission tests and customer acceptance. No GxP status is claimed.Useful adoption can connect the network
If partners can reuse evidence with permission, each successful workspace can make the next handover easier. National coverage is a long-term ambition, not today’s footprint.
Network-value hypothesisTHE DESIGN RESPONSE
Make participation simple, data portable and organization boundaries clear.
Prove it through active counterparties, repeat collaboration and lower onboarding effort.THE PILOT SCORECARD
Measure the workflow.
Not the presentation.
EFFORTDossier preparation time
Baseline vs. pilot median hours per comparable batch.
QUALITYEvidence rework
Missing links, repeated requests and correction rate.
ADOPTIONRepeat useful work
Completed second and third batches, not registrations.
BUSINESSWillingness to pay
Paid conversion, collections and support cost per account.
THE PLATFORM PLAN
Start useful.
Earn the right to scale.
A phased implementation makes the national ambition testable. Timing is indicative from project start, not a promise of delivery.
01
FIRST 3 MONTHS
Prove the workflow
Agree the legal scope and pilot requirements. Build source records, batch-to-sample links, review tasks and controlled sharing.
GATE TO PROCEED
Signed pilot scope, baseline measures and minimum legal, privacy and security checks before live data.
02
MONTHS 4–6
Make it repeatable
Test onboarding, report amendments, evidence exports and support. Iterate through real, authorized batch workflows.
GATE TO PROCEED
Target at least two accepted paid deployments with no unresolved critical security issues.
03
MONTHS 7–12
Build the first network
Convert useful pilots into recurring accounts. Add suppliers and independent labs through permissioned participation.
GATE TO PROCEED
Repeat use, collected payments, evidence quality and sustainable onboarding effort.
04
YEAR 2 & BEYOND
Expand with evidence
Standardize integrations and selected workflows. Grow across independent supply chains, not one giant bespoke deployment.
GATE TO PROCEED
Retention and measurable customer value support each new module and wider rollout.
Scale is a decision, not a default. Narrow or stop if customers will not pay, data cannot be shared lawfully, support costs overwhelm value, or the workflow does not improve on existing tools.
A SIMPLE MODEL TO TESTSoftware subscription.
Software subscription.
Focused implementation.
A processor or exporter pays for its workspace, with invited supplier, lab and reviewer participation. Onboarding is scoped separately. Prices require validation. The platform plan does not depend on owning a laboratory or transformation center.
TRUST BY DESIGN
Clarity is part
of the product.
RifTrace’s role is to make evidence usable and responsibility visible. A green screen must never substitute for a legal or quality decision.
Private infrastructure, not an authority+
RifTrace is a privately conceived platform. It has no asserted government affiliation, ANRAC approval, official mandate, customs integration or authority API access. Its records support operations and do not replace statutory records unless expressly accepted by the relevant authority.
Independent testing, accountable human review+
Laboratories perform tests and authorize their own reports. Operators and qualified reviewers assess applicable requirements. A report, hash, low THC figure or internal status does not establish universal legal compliance or export approval.
Permissioned data, verified controls+
Production requires role-based access, tenant isolation, review logs, tested recovery and suitable privacy arrangements. Personal data and cross-border transfers need assessment under applicable Moroccan requirements. These are implementation requirements, not verified production claims.
A demonstration, not claimed traction+
The existing prototype illustrates intended workflows with fictional records. It is not a validated production system. No live customers, paid deployments, partnerships, regulatory approvals or financial results are asserted on this website.
FROM VISION TO WORKFLOW
See the operating
layer take shape.
Explore the investor prototype and follow how
the evidence connects.
Fictional records. No live integrations or official approvals.