Product truthLIVE, AVAILABLE, PRIVATE, VAULTED
The Product Registry drives public state. AVAILABLE means a functioning public journey with disclosed limits. PRIVATE requires authorized access. VAULTED work is retained internally but excluded from public discovery until a separate release gate passes.
Review the directory →SourcesFollow-through, not implied endorsement
Current public claims identify a source and checked date where appropriate. Official records remain owned by their source authority; FTN context is labelled separately.
See the source pattern →Private boundariesSeparate by purpose
Community Connect, vaulted products, ibis private content, authentication and owner controls are not placed in the public offline cache or reused silently across products.
AIMethod and provider visibility
Deterministic routing is not called generative AI. ibis shows local/on-device/server method boundaries. Generated output is a draft until a user reviews and publishes it. When a response draws on a real live source, its own compact evidence card names that source, shows when the source itself was published (separately from when FTN retrieved it), how it was retrieved, and a real confidence basis — or the explicit label “Not assessed,” never a percentage that isn’t real. A fallback or unavailable route is always disclosed, not hidden. Hidden prompts, credentials, internal provider retry attempts and private conversation content are never shown in that card or retained beyond an ordinary reply.
Responsible AI →Browser storagePreferences and local work
Country choice, last public task, drafts, saved sources and some creative projects may live in your browser. They are not cloud backups. Private PWA caching is disabled.
AnalyticsCloudflare delivery telemetry
The production host currently exposes Cloudflare Web Analytics/delivery telemetry. FTN does not use that as permission for sensitive replay, cross-site advertising or unrelated product profiling.