Skip to main content
Str8shiftDigital

Str8shift flagship product · live field report · updated 2026-08-20

Know what changed.
Understand why.
See what follows.

Str8n turns reporting and official records into geographically honest, source-linked event dossiers. It makes a changing situation legible: what happened, where it happened, what the evidence supports, what remains uncertain, and the signals that would change the read.

Say it straighten. For readers, analysts, and teams, it is one shared event model with a receipt behind every public decision. It is also Str8shift's flagship product and portfolio build: live software we operate while it grows.

Live on web, iOS, and AndroidTwo-hour GitLab newsroom cycleSource links stay attached

Why it exists

Situational awareness starts with the event, not the feed.

A moving situation arrives as headlines, clips, official statements, posts, and opinions. The reader or analyst is left to figure out which claims repeat the same source, what is confirmed, what is framing, and whether the loudest story is actually the most important one.

Str8n organizes that material around the event instead of the outlet. It does not tell you what to believe. It shows what the available evidence supports, where reporting diverges, what remains uncertain, and why the situation may matter beyond today's headline.

01

The five-minute catch-up

Open the Brief, see what changed, and decide which events deserve a deeper read. No infinite feed required.

02

The situation that is moving

Check the factual core, track uncertainty, compare how outlets frame it, and follow the linked evidence before you repeat the claim.

03

The team decision

Start from a structured event record instead of a pile of tabs: sources, location meaning, analysis, confidence, and the signals that would change the read.

Why it is different

Not a headline feed, bias chart, or alert firehose. A model of what is happening.

Many products collect, compare, summarize, or alert. Str8n joins those useful functions to one evidence-bound event record. The globe, Brief, analysis, and source links all read from the same dossier, so a person can inspect the reasoning and its limits instead of taking a score or summary on faith.

01

The event model

Articles describe events. Str8n models them.

Related reporting is organized around one living dossier: what happened, where it happened, which claims are supported, how coverage differs, what remains uncertain, and which changes would materially alter the read.

02

Location meaning

Every puck has to explain why it is there.

A marker may represent an event site, a reported area, or a contextual organization anchor. Str8n labels that meaning instead of presenting every coordinate with false precision. If a location cannot be supported, the event does not get a public puck.

03

Evidence roles

A second link is not always a second source.

Independent reporting, official documents, firsthand claims, and discovery signals do different jobs. An official announcement can establish what an institution said. It cannot quietly count as independent confirmation that the statement is true.

04

Publication receipt

The published decision has a record too.

A useful summary is not automatically a public fact. Generation, evidence, location, policy, and publication stay separate so a dossier can be audited, corrected, withdrawn, or updated without quietly rewriting its history.

The Method

Four questions. One straight answer.

News never arrives neutral. Every headline reflects a choice about what to emphasize and what to leave out. Str8n keeps reporting, generated analysis, location decisions, and publication policy separate so one cannot quietly impersonate another.

01

Evidence packet

What can be proven?

Publisher feeds, official alerts, and permitted public sources become evidence records with links, timestamps, excerpts, rights, freshness, and verification state.

02

The str8

What actually happened?

Corroborated reporting becomes a plain account of the event. Confirmed facts stay separate from interpretation, forecast, and uncertainty.

03

Analysis

How is it being framed?

The dossier compares reporting angles beside the factual core, points to the language behind an interpretation, and explains why those choices matter.

04

Policy gate

Is it safe to publish?

A fixed automated editorial policy checks evidence, scope, location, freshness, and publication state. People can audit, correct, or withdraw a decision without becoming a bottleneck for every story.

Every event also carries two scores: magnitude, how much it actually moves the world, and a spin score, how hard the media field is working it. The loudest story and the most important story are rarely the same one. Str8n shows you both.

What's Inside

Built for the way people actually follow a story.

Use the world as the filter

Turn and zoom the hand-built globe to change the events in view. Exact event sites, broad reported areas, and contextual entity locations remain visibly different.

Catch up without doomscrolling

The Daily Brief ranks current events by real-world magnitude, not by outrage, repetition, or whatever is winning the feed that hour.

Open one story and get the context

Each dossier keeps the factual core, reporting angles, incentives, scenarios, confidence, and source links together in one readable record.

Ask for focus without rewriting the facts

AI Lens can adjust depth and perspective while citations, evidence rules, access limits, and deletion behavior remain controlled by the product.

What has actually been built

One event record. Four serious systems.

The visible app is only the front door. Str8n also includes the newsroom that assembles events, the evidence model that keeps decisions inspectable, and the access foundation needed to serve readers, analysts, and professional teams.

01

Live product

A complete cross-platform view of the world

The globe, deep zoom, filters, Daily Brief, dossiers, AI Lens controls, cited brief analysis, and shareable Str8 cards run across web, iOS, and Android from one product codebase.

02

Newsroom engine

A pipeline that prepares the news before you ask

Source adapters gather permitted reporting, cluster related coverage, build validated revisions, and schedule editorial work in batches. The app reads prepared intelligence instead of improvising an answer on demand.

03

Trust layer

Receipts for the decisions people usually have to trust

Source, location, analysis, policy, and publication decisions remain separate and inspectable. A story can be withheld, corrected, or withdrawn without quietly rewriting its history.

04

Data foundation

Built to serve readers, teams, and future data partners

Authentication, server-owned access, bounded AI use, and structured dossiers create a path from a useful consumer product to professional workspaces and licensed data or API surfaces. Those team-facing access paths are being shaped, not sold as a public API today.

One engine, three ways in

Useful for a reader. Structured enough for a team.

A reader can use Str8n to understand a major event before work. An analyst can inspect the linked evidence, uncertainty, and framing. Under the same screen, each dossier is structured intelligence with separate source, location, analysis, policy, and publication receipts.

That creates three honest product paths: a consumer app people return to because it respects their attention; deeper situational awareness for professionals; and, as the offering is defined, team workspaces or licensed data and API access. The last path is intent, not an availability claim.

Live product, honest status

A public product with operational honesty.

Live

Reader experience

The public product includes the globe, deep zoom, Brief, dossiers, share cards, authentication, server-owned access controls, and AI Lens controls across web, iOS, and Android.

Live

Editorial core

The pipeline gathers configured permitted sources, clusters evidence, validates dossier revisions, and records an automated editorial decision separately from generation. Its GitLab production lane runs on a recurring two-hour schedule.

Gated

Public newsroom

Production accepts current dossiers with an exact publication receipt and no withdrawal receipt. Empty stays empty. Demo stories remain isolated behind an explicit demo flag.

Next

Coverage and access

The active work is broader, balanced source coverage and the next product surface: the shape of team workspaces, data licensing, and API access. Those commercial paths remain deliberately unfrozen.

Flagship product, portfolio proof

Not a mockup. Not a client case study. A live product we operate.

Str8n is the clearest expression of how Str8shift approaches real-time data, complex trust boundaries, automation, and cross-platform product design. The operational details below are a snapshot of the live build, not a claim that every future commercial surface has already shipped.

Live

Public product

Web, iOS, and Android

2h

Production cycle

GitLab newsroom schedule

11

Current categories

A broad event picture

3

Product paths

Reader, analyst, team

2026-08-19

Preserve publisher-supplied excerpts

Source records now retain permitted publisher excerpts where available, making the source layer clearer without treating the product as a republishing machine.

2026-08-18

Bring cited conversation to the Brief

The product added a voice-analysis surface designed to keep a conversation tied to the prepared dossier rather than turning it into an unbounded chat answer.

2026-08-13

Move the production newsroom to GitLab

The recurring newsroom lane now runs from GitLab on a two-hour cadence, shifting the operational center of gravity away from a local machine and the older GitHub lane.

2026-08-13

Open the source discovery frontier

Str8n added a controlled way to discover new publishing sources, preserving a receipt for where every candidate came from before it is considered for the product.

2026-08-11

Make publication and source rights visible

The publication layer now carries clearer source-rights and account constraints, reinforcing the distinction between a link, a permitted excerpt, and public evidence.

Counts and entries are a snapshot as of this field report's date. The product keeps moving; the page catches up on purpose.

Straight answers

What people usually ask once they understand the idea.

01

What is Str8n?

Str8n is a source-backed situational-awareness product. It turns reporting and official records into geographic event dossiers that show what changed, what the available evidence supports, what remains uncertain, and what signals could change the read.

02

How is Str8n different from a news aggregator?

A typical aggregator collects headlines. Str8n organizes reporting around the underlying event. It separates corroborated facts from framing and analysis, ranks events by magnitude, preserves source receipts, and shows when a location or forecast is uncertain instead of smoothing those details away.

03

Does Str8n decide which news outlet is right?

No. Str8n is not a truth score or a left-versus-right label. It shows the factual core supported by the available evidence, identifies meaningful differences in framing, and links the language behind those observations so the reader can inspect the reasoning.

04

Does AI automatically publish news in Str8n?

Generation and publication are separate. Drafts must pass contract, evidence, scope, geography, freshness, and policy checks before they can become public. The normal gate is automated and receipt-backed, while authorized people can audit, correct, withdraw, or override a decision.

05

Who is Str8n for?

For readers, analysts, and teams. A reader can use the Brief and globe to catch up quickly; an analyst can inspect evidence and framing; a professional team can work from structured event records rather than rebuild context from a stream of links.

06

Can a team use Str8n as a data layer?

That is an intended product path, not a public API promise. Str8n is building the structured, provenance-conscious event foundation that can support team workspaces, licensed data, and API access as those offerings are defined.

07

Why is Str8n also a portfolio project?

Str8n is Str8shift Digital's flagship product and portfolio build: a live system we operate while it grows. It demonstrates how we approach real-time data, trust boundaries, automation, cross-platform product work, and evidence-first design. It is not client work or a mockup.

08

Why is a Str8n marker located where it is?

Every public marker carries location meaning. It may represent an exact event site, a broader area named in reporting, or a contextual entity location such as an organization headquarters. Str8n labels the distinction so an approximate or contextual point is never presented as a precise incident location.

09

Does every source count as independent confirmation?

No. Str8n gives sources different evidentiary roles. Independent journalism can corroborate an event, an official document can establish what an institution announced, and a firsthand or social claim may remain an unverified signal. Multiple links do not automatically become multiple independent confirmations.

Start with the live product

Open the live product. Shape the next layer.

Str8n is live and actively evolving. Use it to get a clearer picture of the world, or tell us what a team, data, or API layer would need to make the product useful in your work.