Inspiration
Ops teams get policy memos that mix vendors, dates, and open asks. The useful output is a short brief: what it says, and who does what next. SovereignBrief is a new project started in the Hack Apertus window (1–16 Oct 2026) for that job.
What it does
Paste a policy or ops note (or a small PDF) and get a structured action brief: summary, risks, decisions needed, five next actions, and open questions. An optional second language can be requested (EN, HI, or DE). A static GitHub Pages page shows one brief already produced from samples/sample_policy.txt. That page does not call a model.
How we built it
Python and FastAPI. The live path calls Switzerland’s open Apertus model through the Hugging Face router.
- Preferred id
swiss-ai/Apertus-v1.5-8Bwas not on the router (a chat call returned HTTP 400; the id is absent from the router model list). - The working route used for the sample is
swiss-ai/Apertus-8B-Instruct-2509via Public AI (:publicai). - That route is not marked free on the router (about $0.10 / $0.20 per million input/output tokens). The one sample call on 2 Oct 2026 succeeded on included free-account monthly credits. No credits were purchased and no card was added. HTTP 402 would stop the call.
- A local OpenAI-compatible
APERTUS_BASE_URLis the sovereign path (for example vLLM). It is documented, not required for the static demo.
Challenges we ran into
The v1.5 8B id was not routable, so the app retries exactly one documented Apertus route and stops. GitHub Pages cannot run FastAPI, so the public demo is a static snapshot of a real saved brief, not a fake live chat.
Accomplishments that we're proud of
One real sample memo was briefed. The summary returned was: “Draft update to remote vendor access & document retention (comments due Fri).” Five next actions were kept. Risks, decisions, and open questions from that run were not stored, so the static page does not invent them.
What we learned
Check the router model list before assuming a model-card id is callable. A static snapshot is an honest demo when the host cannot run the API.
What's next
Keep the local app pointed at a self-hosted Apertus endpoint so the same brief can run without a US inference router.
Log in or sign up for Devpost to join the conversation.