Features and their status

This is everything NewsForge is planned to do, grouped by job. Each feature states its status. Specified means an accepted specification with acceptance criteria exists; it does not mean the feature is built.

What the statuses mean

Every feature on this site carries one of four statuses. None of them means available.

Status: In build
Work has started from an accepted specification. Not ready for use yet.
Status: Specified
An accepted specification with acceptance criteria exists. Building has not started yet.
Status: Planned
On the roadmap, with a written plan in the specification, but no build is scheduled yet.
Status: Exploring
Research only. There is no committed plan yet.

The desk

Where stories will be planned, written, edited and approved.

Newsroom queue and story workspace, Status: Specified

Designed so every story shows its state, owner, deadline and any hold before anyone opens it.

Design notes

Each saved version is specified to be immutable and to carry its provenance: who wrote each sentence, which model touched it, and who approved it.

In the specification

  • State, owner and deadline beside every story in the queue
  • Immutable versions with a full history
  • Embargo, legal and page-lock holds visible in the queue

Collaborative Bangla editor, Status: Specified

Planned: reporters and sub-editors working on the same story at once, with offline filing.

Design notes

Designed so that no word is lost across an app crash or a day offline.

In the specification

  • Real-time co-editing
  • Offline filing that will sync when the network returns
  • Accept or reject each suggested change, with its author

Desk operations, Status: Specified

Assignments, the budget board, bureaus, shift handover and a breaking-news mode are planned to sit in one place.

Design notes

Gates such as the two-check breaking gate and named approvals are designed to sit inline in the work, so the safe path is also the fast path.

In the specification

  • A budget board by desk or by edition
  • Bureaus that will first-edit and forward to the head office
  • Handover notes between shifts and a breaking mode

Wire desk and agency feeds, Status: Specified

Agency copy is to land in one triage queue, routed to the right desk.

Design notes

Designed for the take, kill and embargo practice of news agencies. A kill from an agency will be traced to every story that used the copy. Which feeds a newsroom receives will depend on its own agency agreements.

In the specification

  • Routing by desk and topic
  • Take, kill and embargo handling
  • Legacy Bijoy text converted on arrival

The field

Designed for reporters and stringers on a phone, often on a bad network.

Reporter app, Status: Specified

A phone app planned for staff reporters and district stringers, designed to file on a weak network.

Design notes

Every filing is specified to return a signed receipt, so a stringer will have proof of what was sent and when.

In the specification

  • Offline work that will send when connected
  • Assignments and desk queries in one inbox
  • Filing through WhatsApp is planned, subject to a messaging provider

Channels

One story, planned to be shaped and released for every place it appears.

One story, many channel variants, Status: Specified

The plan: write the story once, then shape a channel variant for web, print, Facebook, Instagram, LinkedIn, push alerts and the newsletter.

Design notes

Each channel variant is specified to have its own style profile, copywriting rules, workflow and approver. A consistency check will compare every channel variant with the story's FactSheet: a channel variant may say less, never more. Social variants are to be written and approved here; posting will stay manual until publishing adapters exist.

In the specification

  • Style and copy templates per channel
  • A version history and an approval for each channel variant
  • A fact-consistency check before release

Web publishing through Loom, Status: Specified

Approved web variants are to be pushed to Loom, a headless CMS, each delivery returning a signed receipt.

Design notes

A WordPress channel is specified as a fallback, so a newsroom will not be tied to one website system.

In the specification

  • Push on approval, retract with a record
  • A signed receipt after every delivery
  • A WordPress fallback channel

Print variants are specified to go to NewsForge Pages (print layout), a separate product, and the plated pages are to come back as the record.

Design notes

The e-paper is specified to be the exact printed page and the archive of record. A kill, a hold or a legal flag after sending will withdraw the story from layout and keep it off the e-paper. NewsForge Pages itself is planned, not specified.

In the specification

  • Send to layout with placement facts
  • Changes after page lock will need a print acknowledgement
  • The e-paper will be the exact printed page

Trust and safety

AI, corrections, legal risk and security, designed to be held to account.

AI under a policy engine, Status: Specified

Designed so the newsroom decides, per desk, content kind and channel, how far AI may go: off, suggestions, or drafts behind a human gate.

Design notes

Every AI step is specified to be logged with its model, its inputs and the policy decision. AI text will never appear under a human byline, a push alert will never be sent by a machine, and no channel variant will be allowed to state more facts than the FactSheet.

In the specification

  • Levels of AI help, set per desk, content kind and channel
  • A named human will approve before release
  • Full provenance for every AI run

Corrections, legal flags and embargoes, Status: Specified

Corrections, legal flags, takedown clocks and embargoes are specified to apply to every channel a story lives on.

Design notes

Embargoes are designed to reach print too: an edition will not go on sale holding a story whose embargo lifts later, unless two people override it.

In the specification

  • A correction will reach every channel
  • Legal flags will block release until cleared
  • Takedown clocks with a named owner

Security and trust, Status: Specified

Designed so each newsroom's data is kept apart and every action is written to an audit chain.

Design notes

The specification requires an append-only, hash-chained audit log and signed receipts, so a disputed action can be checked later.

In the specification

  • Isolation between newsrooms
  • A hash-chained audit log
  • Export of every story, version and provenance record in open formats

Platform

The Bangla text engine and configuration that will sit underneath everything.

Text engine designed around Bangla, Status: Specified

Designed to handle Bangla correctly everywhere: input, search, spelling, numerals and 12-hour time.

Design notes

Legacy Bijoy text is to be detected and converted to Unicode on arrival. An early trial on synthetic text cleared the converter to go ahead with conditions; real newsroom files will be needed to confirm it.

In the specification

  • Bijoy to Unicode conversion
  • Search that finds Bangla names across spellings
  • Bangla numerals and 12-hour time

Everything configurable, Status: Specified

Workflows, gates, thresholds, labels and house style are designed as settings a newsroom edits, not code.

Design notes

Every setting is specified to be typed, versioned and audited, with an editor in the admin screens. Style profiles and entitlements will be configuration too.

In the specification

  • Workflow and gate settings per desk
  • House style profiles per newsroom
  • Entitlements packaged by configuration

The NewsForge family

Separate products that would sit beside NewsForge. None of them is specified yet.

NewsForge-AI Desk, Status: Planned

A separate product planned for crawling, clustering and synthesis from licensed or permitted sources.

Design notes

It would reach NewsForge only through a defined contract, and anything it produces would enter the desk as a candidate for people to review.

Scope under consideration

  • Licensed or permitted sources only
  • A specification of its own, not yet written
  • Candidates for review, never published directly

NewsForge-Social, Status: Planned

A separate product planned for publishing and scheduling on social platforms.

Design notes

Writing and approving social variants is already in the NewsForge specification. This product would add posting from NewsForge; until then posting will be manual.

Scope under consideration

  • Posting adapters per platform
  • Scheduling
  • Retraction across platforms

NewsForge Pages (print layout), Status: Planned

A separate print-layout product, planned to take NewsForge print variants to plated pages and e-paper.

Design notes

Planned and parked for now: the NewsForge side of print is specified, NewsForge Pages is not specified yet. It is to be built on KaritKarma's Pressable layout tool, which is not the WordPress host of the same name.

Scope under consideration

  • Page layout and typesetting
  • Print-ready files and plated pages
  • E-paper pages made from the plated pages

NewsForge-Video, Status: Exploring

An idea to explore: video made from a story, with clips, Bangla captions and rights tracking.

Design notes

Research only. There is no committed plan yet, and whether it would be built is not decided.

Scope under consideration

  • Bangla captions
  • Rights and expiry per clip
  • Short vertical clips from a story

NewsForge-Ad marketplace, Status: Exploring

An idea to explore: booking and placing advertising for print and digital.

Design notes

Only three newsroom hooks for advertising are in the current specification. The marketplace itself is research only, with no committed plan yet.

Scope under consideration

  • Ad positions on the page plan
  • Separation of advertising from news
  • Booking and proofs