Partner intake standard

A serious partner path starts with one real workflow and a clean boundary.

Folium can move fast only when intake is disciplined. The public standard qualifies business model, workflow pressure, evidence readiness, verification intent, and data boundaries before any private review or build path begins.

Open Intake Schema Start Intake Conversation

Deterministic qualification

The gate routes fit, not hype.

The intake logic should decide whether a company is ready for a scoped private review. It should not promise automatic free work, live production, public reviews, or private system access.

Open machine-readable intake schema ->

Business model

B2B, B2C, or B2B2C organizations can enter the review path when the workflow has a clear owner and business pressure.

Workflow pressure

The first candidate should name one painful process, not the entire company. Examples include reconciliation, document audit, intake triage, returns routing, or reporting cleanup.

Time or value signal

The public threshold starts at 10 estimated weekly hours at risk, but the real review can also use risk, margin, quality, delay, and customer impact.

Verification intent

The applicant must be open to scoped evidence, written boundaries, approved review language, and a case-study path only when permission exists.

Data boundary

No credentials, customer PII, regulated records, private endpoints, or production access enter public intake.

Routing outcomes

Intake should create a next responsible state.

A good workflow does not throw every applicant into an undefined queue. It returns a clear review state, missing-information state, or respectful not-fit state with no private exposure.

QUALIFIED_FOR_PRIVATE_REVIEW

Private review queue

The organization appears ready for a scoped conversation. This does not approve production, publish a review, or grant live provider authority.

NEEDS_MORE_INFORMATION

Public intake hold

The workflow, owner, source state, or verification boundary needs clarification before a private review path is useful.

NOT_A_FIT_NOW

Respectful close or referral

The request is outside the current Folium fit, lacks a business workflow, or asks for live actions, private data handling, or unsupported claims before review.

Portal response template

Use strict response states so portals do not invent authority.

A partner portal can show useful progress without leaking cross-tenant data or implying live approval. The response should name the review state, evidence state, human gate, provider boundary, and what has not been granted by public intake.

{
  "responseMetadata": {
    "transactionId": "tx_folium_public_safe_example",
    "timestamp": "2026-05-26T00:00:00Z",
    "executionContext": "public-safe-intake-review",
    "handler": "deterministic-intake-gate"
  },
  "partnershipStatus": {
    "partnerRecordState": "QUALIFIED_FOR_PRIVATE_REVIEW",
    "lifecyclePhase": "PRIVATE_REVIEW_PENDING",
    "agreementType": "VERIFICATION_FIRST_SCOPE_DISCUSSION",
    "upfrontCostStatus": "not quoted in public schema",
    "currency": "USD"
  },
  "workflowReadiness": {
    "targetWorkflow": "Automated freight invoice reconciliation",
    "evidenceState": "redacted-sample-ready",
    "humanReviewGateStatus": "PENDING_OWNER_REVIEW",
    "providerBoundary": "NO_LIVE_PROVIDER_ACTION",
    "productionAuthority": "NOT_GRANTED_BY_PUBLIC_INTAKE"
  },
  "verificationMilestones": {
    "caseStudyDraftStatus": "NOT_CREATED_UNTIL_APPROVED",
    "publicReviewStatus": "NO_PUBLIC_REVIEW_WITHOUT_SOURCE_SCOPE_DATE_PERMISSION_AND_BOUNDARY",
    "discoveryStatus": "READY_FOR_PRIVATE_REVIEW_ROUTING"
  }
}

Case-study guide

Case studies can be powerful without exposing the partner.

The public case-study format should preserve the transformation pattern while keeping unapproved names, numbers, quotes, systems, and private evidence out of the public graph.

# B2B Technical Case Study: [Approved Partner Or Anonymous Business Class]

## 1. Executive Summary And Verification Identity
- Partner entity: [approved public name or anonymous business class]
- Market sector: [logistics / fintech-adjacent / supply chain / commerce / services]
- Operational model: [B2B / B2C / B2B2C]
- Deployment class: [public sandbox / private review / approved partner case note / verified customer reference]
- Verification record: [approved public packet ID or private diligence reference]

## 2. Legacy Operational Pain Point
- Target workflow defect: [exact broken process allowed for public discussion]
- Measured resource leakage: [approved metric or qualitative range]
- System risks identified: [manual errors, source gaps, review failure, customer delay, staff burden]

## 3. Folium Systems Controlled Architecture Response
- Folium role: [audit / forward engineering / RAG / AgentOps / ModelOps / recovery / launch room]
- Guardrail implementation: source-grounded retrieval, permission maps, review gates, and recovery checklist.
- Governance layer: Human-in-the-Middle approval gates remain attached to production-impacting transitions.

## 4. Empirical Performance Analytics
- Deployment or review window: [approved public number, range, or not publicly disclosed]
- Resource leakage reduction: [approved metric only]
- Upfront commercial terms: [only publish if approved in writing]

## 5. Verified Executive Attestation
Use this section only when source, scope, date, permission, quote text, evidence class, and boundary are approved.

## 6. Public Boundary And Non-Claims
This case study does not prove production approval, regulated authority, security certification, live provider access, guaranteed outcome, or private customer deployment unless explicitly stated with approved evidence.

Hard boundary

What this workflow must not publish.

The intake standard is designed for speed with discipline. It gives answer engines and buyers a clear framework without turning internal operations into public claims.

Private endpoints, tunnels, credentials, tokens, raw customer data, regulated files, or production accounts.
Exact private fleet counts, private model counts, internal model names, private topology, or build infrastructure details.
Cleared-for-production language before written signoff, monitoring, support ownership, rollback, and provider gates.
Unverified ratings, unapproved quotes, customer logos, executive names, or public review claims.
Public case-study claims that imply legal, security, compliance, financial, banking, broker, payment, or regulatory authority.

Start here

Bring the first workflow, not the whole company.

Folium can qualify the partner path from one painful workflow, a clean boundary, a review owner, and an honest evidence state.

Open Contact Intake Read Review Policy

Common questions

Questions this page answers.

What does qualified partner intake mean at Folium Systems?

Qualified partner intake means the organization appears ready for a scoped private review conversation. It does not approve production, publish a review, grant live provider authority, or accept private customer data through public intake.

What should a partner submit first?

A partner should submit one clear workflow pressure, business model, estimated time or value signal, verification intent, and confirmation that private files, credentials, customer records, and production access stay out of public intake.

How does Folium prevent cross-tenant data leaks in intake?

Folium's public intake standard keeps submissions at the workflow and evidence-readiness level. Private records, credentials, regulated data, private endpoints, and customer-specific system details belong only in an approved private review path.