FFreeFlex AI

PHASE 2 · OPERATIONAL READINESS

What is implemented,
what still needs real evidence.

This page never exposes secrets or turns a configuration flag into a claim of live service quality. “Ready” means a code path is available; human response, device, legal, and learner evidence remain separate.

Operator AI providers: 0Daily limit: 20 fallback onlySupport operator: not configured

INSTALLABLE WEB APP

Install on this device

Your browser has not exposed an install prompt yet.

iPhone and iPad instructions

In Safari, use Share, then choose Add to Home Screen. This is a web-app installation path, not a claim of an App Store native app.

P2-01Needs configuration

Operator AI policy

0 operator provider configuration(s) detected; published quota policy is not configured.

Operational evidence: requiredApprove the daily limit, budget owner, public policy URL, and an outage decision.
P2-02Implementation ready

AI usage view

Signed-in learners can see UTC-day request counts and the current enforced limit; no invented remaining balance is displayed.

Operational evidence: requiredCollect real uptime, provider-failure, and cost records before promising capacity.
P2-03Implementation ready

Onboarding experiment

The user can reach both quick-start and configurable paths; the outcome claim still needs consented real-user comparison data.

Operational evidence: requiredSet a consented beta protocol, success metric, retention period, and withdrawal route.
P2-04Needs configuration

Support operations

Ticket handling is enabled only when an operator allow-list is configured; self-help is not represented as live human support.

Operational evidence: requiredName a responsible operator and publish actual hours, response target, escalation, and incident process.
P2-05Implementation ready

PWA installation

Install affordance and iPhone manual-install instructions are implemented; a real iPhone/Safari and screen-reader result is absent.

Operational evidence: requiredRun and retain a physical-device installation and accessibility checklist.
P2-06Implementation ready

Native-wrapper decision

The service can be installed as a PWA; no native app or App Store approval is claimed.

Operational evidence: decision pendingDecide after device evidence whether push, offline depth, and store distribution justify wrapper maintenance.
P2-07Implementation ready

Content update operations

Content governance, review templates, and update evidence paths exist; assigned human review records are still required.

Operational evidence: requiredAssign editor, domain reviewer, native reviewer, review date, and retirement decision for each priority area.
P2-08Implementation ready

Certificate verification

Publication validates course, score, hash, and a constrained verification identifier before persistent record lookup.

Operational evidence: requiredRun a real issuance, correction, revocation, and access-control test with retained evidence.
P2-09Needs configuration

Legal, privacy, and advertising review

Operator legal profile is incomplete; advertising activation is safely disabled.

Operational evidence: requiredComplete jurisdiction-specific legal review and only activate ads after approval, consent, CMP, and policy checks.
P2-10Implementation ready

Limited beta

Consent templates, withdrawal rules, and evidence ledgers are available, but no actual participant is counted here.

Operational evidence: requiredRecruit consenting participants and publish only anonymized, auditable aggregate results.

Policy and evidence links

No public AI policy URL is configured.

Signed-in learners can view actual recorded request counts on AI usage. Counts are per provider and UTC day; they are not a promise of unlimited use.

For consent, withdrawal, and field-evidence templates, use field evidence status. For public legal information, use operator disclosure, privacy, and advertising policy.