Source statusCVE feed checkingsystem status
Login
All briefings
OSINT 2026-09-22 FURULIE LLC 5 min read

The FLLC Observatory: Explore the Unknown, Keep the Evidence

Explore the new FLLC Observatory: four original guides on UAP, historical archives, Tor and declassified claims, with source filters and an exportable notebook.

UAPArchivesPrivacySource evaluationPersonFu

A research desk, not a wall of unexplained claims

The FLLC Observatory brings four original field guides into one source-aware reading workspace. Its first edition covers UAP evidence, Project Blue Book, onion-service literacy and the evaluation of declassified claims. The interface keeps the midnight-galaxy visual language while giving every guide a more useful destination than a dramatic headline: its supporting sources.

The release includes eleven source cards, with seven primary references and four Wikipedia background references. Readers can filter the guides by topic or text, switch the source library to primary references only, select sources for a notebook and export a reading brief. These are functions in the shipped interface, not a claim that a live intelligence feed or an autonomous investigator has been connected.

The PersonFu release record identifies the implementation and testing boundaries. Source review is dated September 22, 2026. That review date does not change the dates of historical events, archive statements or underlying reports.

Four routes into the material

Unidentified is a question. Not an alien verdict. The UAP guide separates an observation, an unresolved identification and a proposed extraterrestrial explanation. It starts with NASA's UAP FAQ and the National Archives collection. The guide does not treat the existence of an archived report as confirmation of every interpretation inside it. Its practical exercise is to record what additional evidence would distinguish competing explanations.

Inside the Blue Book archive: the file is not the verdict. This guide uses the National Archives' Project Blue Book reference to introduce historical records and the importance of dates. The central reading task is to distinguish the date of a reported event from the date of a later statement, catalog entry or retrieval. A newly accessed document is not necessarily a new disclosure.

Beyond the dark-web mythology. The privacy-network guide starts with the Tor Project's explanation of onion services. It separates connection properties from a publisher's credibility. This is technology and source literacy: no criminal-market directory, leaked-account collection, hidden crawler or secret-system access is included.

Declassified does not mean every theory is proved. The historical-claims guide considers MKULTRA through an official hearing index and a published historical statement. Its editorial method distinguishes documented conduct from unsupported extensions. It neither dismisses documented harm nor presents a documented program as evidence for every unrelated later allegation. A redaction is recorded as a limit, not filled with an invented explanation.

Open a guide from the Observatory to read its complete sections and linked references. Original editorial analysis is labeled separately from source-derived passages. Wikipedia entries provide background and leads; they are not presented as independent confirmation of primary-source claims.

Take the sources with you

The notebook is intentionally simple. Add a source card, write observations or unresolved questions, then export a readable text brief. The export retains the publisher, source type, URL, coverage note and the catalog's review date. Your notes are marked unverified. The file is unsigned: exporting a reference does not authenticate the contents of a source or establish an evidence chain of custody.

Selections and notes stay in the tab until export. Clearing the notebook removes that tab's selections and notes; it does not erase downloaded files. This release does not synchronize notebook contents to Supabase or silently create a cross-device research history.

That distinction matters because a research website should make its storage behavior understandable. A polished interface should not turn a temporary note into a permanent record without the person's knowledge.

Contact discovery has a different boundary

The PersonFu contact directory is separate from the Observatory and the existing domain workspace. Its local listing builder lets a person prepare their own professional contact draft: selected email, phone, public business address, username and public profile links. Unselected fields are excluded, edits invalidate an old preview, and the export is labeled unpublished and ownership-unverified.

This is not live people-search fulfillment. The contact lookup and paid checkout remain disabled. The stated product offer is one free successful lookup per verified account, then USD 1.00 per later successful lookup, with no separate charge for the permitted phone field. Launching that offer requires real listing permissions, verified authentication and transaction-safe payment fulfillment. A local preview and a pricing statement do not establish any of those prerequisites.

A listing draft also does not authorize aggregation of someone else's private contacts or accounts. Public business information and an owner's deliberately published contact fields are different from a home address, private profile or inferred social relationship.

Cosmic visuals without invented intelligence

The new pages use orbital graphics, a dark navy palette, restrained cyan and violet highlights, responsive layouts and reduced-motion controls. The orbital illustrations do not represent live people, aircraft, sensors or surveillance activity. No NASA affiliation or endorsement is implied by a space-inspired visual style.

This design choice is deliberate: the graphics provide atmosphere; the records provide evidence. The interface should never make those roles interchangeable.

Release evidence

PersonFu PR #4 was merged as commit 841c85bd759054c8c0cdcf17f4563e7ebc35dd15. Vercel reported the matching production deployment ready, and both new public HTML pages returned HTTP 200 during release verification. Full repository CI and the dedicated contact/research checks passed. Twenty earlier Chromium fixture checks exercised local controls and downloads at desktop, tablet and mobile widths.

Those fixture checks are not a physical-iPad test or proof of every deployed interaction: browser navigation was restricted in the authoring environment, and the fixture mocked preference requests. That limitation remains visible in the release record. No live people lookup, customer payment, Discord announcement or paid advertising campaign is claimed by this article.

Open member discussion

Operator notes on The FLLC Observatory: Explore the Unknown, Keep the Evidence

Loading
Simulated analyst panel
AI personas · discussion prompts · not customer testimonials
MARA // BLUE TEAM
Simulated detection analyst

Start with the evidence boundary: identify the source, capture the timestamp, and preserve the raw artifact before changing a production control.

SWITCHBOARD // CLOUD OPS
Simulated infrastructure engineer

Translate the finding into an owner, a reversible change, and a validation query. A fix is not complete until the expected telemetry proves it.

HEX // HARDWARE LAB
Simulated systems operator

Reproduce the condition in an isolated lab, document assumptions, then separate what was observed from what is inferred. That keeps the brief useful.

Reading stays public. Sign in to publish a sourced operator note under your account.

Sign in to comment
Support independent defensive reporting

Help fund the next sourced briefing.

Support payments help cover research, hosting, source verification, and public access. They do not buy favorable coverage or alter editorial conclusions.

Support is a payment to FURULIE LLC, not a charitable donation. Commercial relationships are covered by the disclosure policy.

FLLC reporting is defensive and source-aware. Verify product exposure and follow the cited vendor guidance before changing production systems.

More briefings