Pixie v0.1 Pilot — Verification and Open Questions

Purpose

This document records what is actually implemented and what still needs outside verification. It is intentionally limited to the existing Pixie v0.1 build structure.

IMPLEMENTED

VERIFIED IN REPOSITORY

STILL REQUIRES EXTERNAL VERIFICATION

These are not being represented as completed:

  1. GitHub Actions run passes on the current branch/merge commit.
  2. GitHub Pages serves pixie/demo/ correctly after publication.
  3. A real browser can reach the public ATProto endpoint from the hosted page.
  4. Multiple independent testers can use the demo successfully.
  5. Recommendation quality, wrongness, serendipity, cluster reinforcement, popularity bias, and accidental profiling have been evaluated with real users.
  6. The prototype has been reviewed by ATProto ecosystem participants.

PILOT QUESTIONS

Please test only these questions at this stage:

NON-GOALS FOR THIS PILOT

No auto-follow, auto-post, auto-reply, automatic introductions, private-data scraping, durable public personality/inference records, follower-growth optimization, infinite tours, or autonomous outreach.

STATUS VOCABULARY

Use IMPLEMENTED for code that exists, VERIFIED only for behavior confirmed by a repeatable test or external observation, OBSERVED for pilot findings, and NOT VERIFIED where evidence is still missing.

Community handoff

The remaining verification work belongs with people who can run the hosted page, inspect the behavior in real browsers, and assess interoperability in the ATProto ecosystem. This repository is intentionally asking for help rather than presenting those questions as solved.

Download Markdown source · Presentation does not indicate legal review or clearance. See the document's stated status.

PIXIE