Workflow product · Source provenance

BriefSift

A source-linked briefing desk that turns trusted-source intake into reviewed stories with visible sources, timelines and explicit publication control—rather than an automated news feed.

Next.jsReactPostgreSQLRSSAdmin workflowsGHCR

The product boundary

Automation can collect. A human decides what gets published.

BriefSift is deliberately positioned as a briefing desk rather than an “AI news summarizer.” Intake systems can collect source material and prepare metadata, but a story remains private until the editorial workflow has enough meaningful content, sources and timeline context to pass its publish boundary.

The product is therefore split between a calm public reader and an operational private newsroom where attention is directed toward what needs review, what is blocked and what is actually ready.

Editorial flow

Source intake becomes a public briefing only through explicit review.

01Trusted sources
02RSS / intake
03Private draft
04Sources + timeline
05Readiness / review
06Explicit publish
07Public briefing

Engineering evidence

Workflow software needs operational truth as much as UI.

Evidence

Public reader

Stories, topics, source-linked detail surfaces and published-only read paths.

Evidence

Private newsroom

Source registry, intake queue, story editor, timeline/source controls, dashboard and readiness workflow.

Evidence

Ingestion

Briefing-file and RSS intake prepare material without granting automatic publication authority.

Evidence

PostgreSQL

Ordered migrations, disposable migration proof and explicit runtime/ownership boundaries.

Evidence

Release

Exact-SHA validation, immutable GHCR image publication and a digest-addressed runtime contract.

Evidence

Readiness

Deployment health is DB-aware; process liveness alone is not accepted as proof that the product works.

Release engineering

A green build is not the same thing as a working deployment.

accepted source SHA→exact-head CI→immutable GHCR digest→DB-aware readiness→runtime + ingress smoke

The current repository has this release contract and manual publication path, but the portfolio intentionally does not claim an active production runtime until a fresh deployment receipt exists.

Professional signal

Public product + private operator workflow + data + delivery.

BriefSift adds evidence for full-stack/internal-tools roles: the interesting work sits across public reader UX, protected admin workflows, source ingestion, editorial state, PostgreSQL migrations and release safety.

It is a supporting case study rather than a flagship because the public reader is less mature than the newsroom workflow and no current deployment should be implied.

Selected work

See the flagship product and AI systems case studies.

Back to all work