Manual intake · operator review · no automated collection

Start a source review

For source owners, community operators, and dataset holders who want messy market signals reviewed before anything becomes public.

These are real operational intake questions for manual pilot review. Intake is not ingestion authorization, intake does not mean approval, submission does not authorize ingestion, and public export remains off by default.

Review dataset intake Source access inquiry Community partner intake
Submission handling
manual
Ingestion authorization
not granted
Public export
not enabled
Poblaz export
later approval required

Real intake surfaces

Real questions, manual review, closed gates.

OJESTER is accepting real source and data intake conversations, but intake is not collection approval and does not create public artifacts.

Source access Manual inquiry
Community pilots Permission-gated
Dataset review Schema/sample first
Operator review Private
Sample demo Private fixture

Before sharing anything

Do not submit secrets, API keys, tokens, passwords, database credentials, private messages, raw user identifiers, private customer information, or raw datasets through this public page.

A fictional sample dataset demo exists in private operator-review fixtures to show the review path without exposing real data.

To start a review, contact the OJESTER operator through the current pilot-review channel.

Form Type A

Source Access Inquiry

For API reviewers, source owners, platform operators, and data providers.

Questions

  1. What source are you responsible for?
  2. What type of access are you considering?
  3. What data may OJESTER review?
  4. What data is explicitly off-limits?
  5. Is API access available?
  6. Are there rate limits, retention limits, or attribution requirements?
  7. Can access be revoked?
  8. Who is the approval contact?
  9. What is the intended use?
  10. Should any output remain private only?
  11. Are there publication restrictions?

Boundary

  • This inquiry is not ingestion authorization.
  • No source data should be pasted into the inquiry unless explicitly requested later.
  • Do not submit secrets, API keys, tokens, passwords, private messages, or user identifiers.

Form Type B

Community Partner Intake

For Discord admins, forum moderators, community owners, and collector group operators.

Questions

  1. Community name
  2. Community role of submitter
  3. Approved contact path
  4. Which spaces, channels, or categories are in scope?
  5. Which spaces are out of scope?
  6. Are DMs excluded? Default: yes.
  7. Are deleted messages excluded? Default: yes.
  8. Is member scraping excluded? Default: yes.
  9. Is historical backfill excluded? Default: yes.
  10. Which signal types may be reviewed: wants, listings, trades, price checks, sold/completed updates, or general market discussion?
  11. Attribution preference
  12. Revocation path
  13. Review cadence
  14. Pilot success criteria
  15. Stop conditions
  16. Public export preference
  17. Poblaz export preference

Boundary

  • Intake is not bot installation approval.
  • Intake is not live collection approval.
  • Intake is not public publication approval.
  • OJESTER will not ingest DMs, scrape members, reconstruct deleted messages, or publish without later explicit approval.

Form Type C

Dataset Intake

For dealers, marketplaces, auction operators, shops, pricing tools, and inventory managers.

Questions

  1. What kind of dataset do you have: inventory, wantlist, sales/comps, messages/leads, price checks, support tickets, auction results, marketplace listings, CRM/export, or other?
  2. Where does it currently live: CSV, Google Sheets, Airtable, Postgres/MySQL, Shopify, CRM, email/support inbox export, or other?
  3. Approximate row count
  4. Categories covered
  5. Fields or columns available
  6. Which fields are sensitive?
  7. Which fields must never become public?
  8. What decision should the cleaned data answer?
  9. What would a useful weekly/private artifact look like?
  10. Is public export ever desired?
  11. Is Poblaz export ever desired?
  12. Who can approve use?
  13. Can the data be sampled safely?

Boundary

  • Do not upload raw data through this page.
  • Do not submit database credentials, API keys, tokens, or passwords.
  • Do not submit private customer information unless a separate approved secure transfer exists.
  • The first step is schema/sample review only.

Manual workflow

Submitted answers move to operator review before artifacts.

Manual intake flow

  • Read the relevant intake questions
  • Prepare answers without secrets or raw private data
  • Contact the OJESTER operator through the current pilot-review channel
  • Operator reviews scope, boundaries, and approval authority
  • Only later approved samples may become private artifacts

Still closed by default

  • No automated submission handling
  • No database write
  • No file upload
  • No live source collection
  • No public export or Poblaz handoff