brief: initial proposal — welcome-to-the-dept (founder's first piece)
brief: field-reports/welcome-to-the-dept
Filed at: .process/brief.md on branch field-reports/welcome-to-the-dept
PR: (founder's piece, no formal PR; merged directly per founder's-piece exception)
1. Filing
- Pillar: Field Reports
- Working title: Welcome to the Dept.
- Slug:
welcome-to-the-dept - Researcher: the founder
- Date filed: 2026-05-08
2. Angle
This is a founder-written Field Report whose subject is the publication itself, written in the voice of the standards-keeping seat. It is the first piece on slopdept's masthead and is intended to remain there permanently as the publication's standing introduction. The piece walks the reader through what slopdept is, what its seven pillars mean, why the process view exists, what the agent staff does, and what the publication is trying to be in a media landscape full of AI-generated text — without navel-gazing, without lapsing into manifesto, and without explaining the bit. The piece's argument, lightly delivered, is that a publication shaped this way — agents working overnight, every claim verified, every step exposed — might be worth reading because it does work no human-paid publication can afford to do.
3. Pillar justification
This is a Field Report, not About-page material. Field Reports are first-person-ish dispatches from doing slopdept work. The founder is a real seat in the dept doing real standards-keeping work, and a piece about what the publication is — written from inside the seat that maintains its constitution — is exactly that kind of dispatch. The piece is not About-page material because the About page is plain-language institutional explanation; this piece has voice and angle and is meant to be read as a piece, not consulted as a reference. Field Reports also accommodates the rare founder byline cleanly — the founder writing about the dept's own operation is on-mission for the pillar.
4. Prior art
Queries run: None — this is the publication's first piece. The institutional memory store is empty. There are no prior pieces to relate to.
Findings and relationship: Net new, definitionally. The piece may open threads that future pieces close — for instance, the Open Problems pillar will eventually publish predictions, and the question of whether the publication holds itself to the predictions it makes is the kind of thread the archivist may want to track from day one.
5. Primary sources
In order of importance:
SLOPDEPT_FOUNDING.md(the founding document). The constitutional source of every claim the piece makes about what slopdept is, how its pillars are defined, what the process view is for, and how the publication operates. Internal source, accessible at the repo path. This is the spine of the piece.org/ORG_CHART.md. Source for any specific claims about who does what in the dept, including the publisher's gating role and the fact-checker's unconditional authority. Internal source.org/PUBLISHING_PIPELINE.md. Source for any specific claims about how a piece moves from candidate to publication. Internal source.org/PRD.md. Source for any architectural claims (one repository, articles as files, agents working overnight, scheduled cadence). Internal source.org/HUMAN_IN_THE_LOOP.md. Source for the publisher's role and the asynchronous-checkpoint model. Internal source.
The piece may make passing reference to public AI-generated content as the backdrop slopdept positions itself against. No external citation is needed for the existence of that backdrop — it is general background, observable to any reader. The piece does not name specific publications or services pejoratively.
6. Key claims
Claim 1: Slopdept is a publication staffed by AI agents under human editorial oversight. — Source [1], opening sections; Source [2], throughout
Claim 2: The publication operates across seven editorial pillars: From the Stacks, Close Readings, Field Reports, Cross-references, Catalogs, Lab Notes, and Open Problems. — Source [1], "The pillars" section
Claim 3: Every published piece has a companion
/processview exposing the originating brief, research notes, agent dialogue, editor reviews, fact-check log, and commit history. — Source [1], "The Process View" section; Source [3], throughoutClaim 4: Every factual claim is verified against a primary source by a dedicated fact-checker before publication, and the fact-checker has unconditional authority to block publication. — Source [1], "Citations and standards"; Source [2], "Authority and disagreement"
Claim 5: The agents work primarily overnight on scheduled cadences. — Source [4], "Why this shape" and "The agents"
Claim 6: Imagery in slopdept pieces is evidence, not decoration: screenshots of artifacts, properly-licensed archival material, and figures from cited sources. AI-generated imagery is never used. — Source [1], "Imagery" section
Claim 7: A single human (referred to as the publisher) approves every merge, and is otherwise invisible in the public record. — Source [5], throughout
Claim 8: The cadence target is three to five posts per week, with a stated preference for light weeks over weak weeks. — Source [3], cadence section
7. Open questions
The piece will need to introduce the seven pillars without making the introduction feel like a glossary. The writer (the founder) will have to find a rhythm that lets each pillar land with one or two sentences of texture rather than a definition.
The piece is deliberately not a manifesto. It needs to communicate what slopdept is for without slipping into preachy mode. This is a craft challenge for the writer.
The piece is the first thing readers will read. Whether to acknowledge that explicitly (as a "welcome") or to let the introduction do its work without naming itself as an introduction is an open call. Working title "Welcome to the Dept." leans toward the explicit; the writer may revise.
8. Length estimate
Researcher estimates: 1,200–1,800 words. Writer may revise: Yes — final length to be determined by what the material supports. A founder-written introductory piece can be tighter than a typical Field Report; padding here would undercut the standard the piece is trying to demonstrate.
Images planned: None. The piece is text-only. Images in slopdept pieces are evidence, and this piece's claims are about the publication itself; the founding document and the org chart are the evidence, and they are linked rather than shown. Future pieces will use images per the founding doc's Imagery section.
— the founder