status without theatre
Green does not mean launched. Gated does not mean offered.
A minimal public status surface for the public site and restricted preview infrastructure.
This page records the state of the public surfaces: what is reachable, what is gated, what is pending. It is not an SLA, not a contract, not a marketing page. Where a surface is green, it is functioning for its intended audience — nothing more. Where a surface is gated, it exists but is not public. Where a surface is pending, it is on the roadmap but is not yet operational.
auth.blackmenta.com by separate route.
Four words. Four meanings.
Reachable · functioning
A surface is reachable and functioning for its intended public or gated audience. Green is verified at last-check, not promised continuously.
See full legendExists · not public
Access exists but is not public. Does not imply qualification, allocation, or approval. Routing happens through the appropriate channel, not this page.
See full legendRoadmap · not live
A future item exists in the roadmap but is not operational, launched, or offered. Pending is not a release date; it is an acknowledgement.
See full legendBounded · beta
A surface operates within a deliberately narrow scope — e.g. the AI assistant on a public corpus only, no legal/financial advice. Bounded behaviour, not feature gap.
See voice doctrineIf something breaks, route it cleanly.
security@
Vulnerabilities, abuse of public surface, suspected account-security issue. The first lane when something breaks. Same SLA as the security policy.
security@ → SR.02 privacyprivacy@
Data subject requests, privacy questions, cookie/logging concerns observed via the status page or any public surface.
privacy@ → SR.03 generalhello@
Non-sensitive public status questions, route clarification, page-feedback or “I think this is wrong” reports about a status row.
hello@ → SR.04 reviewerpreview@
Verified reviewer access to fuller operational status, internal incident detail and counsel/diligence-side records under NDA.
preview@ →Operational signals, not launch claims.
Five surfaces, one timestamp. Each row says what is reachable, in which mode, for which audience. The state column is the legend on Sheet 03; it is not a feature scorecard.
Public surface
blackmenta.com and its subpages (home, what, how, who, evidence, voice, security, privacy, legal, terms, contact, brand, trademarks, press). Public record and trust pages available.
Restricted preview
auth.blackmenta.com and reviewer-side surfaces. Invitation-only reviewer access. Routed via preview@ with identity, context and role.
Assistant surface
The controlled assistant on /voice. Public corpus only, no legal/financial advice. Refusal-by-design behaviour is a feature, not a fault.
Security route
Disclosure and incident routing. Reports go to security@blackmenta.com. Scope, evidence and SLA documented on /security.
Operator track
Separate authorised operating entity. Not yet public. Incorporation and authorisation route expected after counsel-led track. The structure exists; the public surface does not.
What the words actually mean.
Four semantic states. Each one says something specific and refuses to imply more. Status pages routinely overload colour to signal hype — this one will not.
Reachable, functioning
A surface is reachable and functioning for its intended public or gated audience. Green is verified at last-check, not promised continuously. Green ≠ launched. Green ≠ supported. Green ≠ complete.
Exists but not public
Access exists but is not public and does not imply qualification, allocation, or approval. Gated routes through a named lane (preview@, legal@) under stated conditions.
Roadmap, not live
A future item exists in the roadmap but is not operational, launched, or offered. Pending is an acknowledgement of intent, not a release date and not a commitment.
If something breaks, route it cleanly.
Three lanes. Same as the route grid above the sheets, restated as the incident-routing protocol. Misrouted reports get rerouted — but the right route is faster, especially under time pressure.
Vulnerabilities · abuse
Vulnerabilities, abuse of public surface, suspected account-security issue. Includes phishing, credential harvesting and spoofed pages.
Data · cookies
Data subject requests, privacy questions, cookie/logging concerns. UK GDPR rights run through this lane (Art. 15–22).
Status questions
Non-sensitive public status questions, route clarification, “I think this status row is wrong” reports and page feedback.
Status is not solicitation.
Status pages drift into marketing pages quickly. The five rules below pin the line: this is a signal surface, not a sales surface. Each row records something this page is not, with the route where the right answer lives.
auth.blackmenta.com by separate route with separate terms.
preview@
Best-effort windows. Not contractual.
Four windows. The same shape security uses in /security, restated for incidents reported via the status page. Targets are best-effort, not promises — faster on critical, slower on cosmetic.
Each row carries a timestamp.
Four entries. Each one records when a piece of the public surface was last verified by a human, not a probe. Status without a date is a vibe; with a date it is a record.
Operational detail is gated.
This page is the public status surface. Internal incident logs, infrastructure diagrams, vendor inventory, runbooks and reviewer-side operational records are released through auth.blackmenta.com — to verified reviewers, counsel and diligence parties under NDA.
Other pages, in any order.
Security · privacy · voice · terms · home.
Responsible disclosure route
Scope, evidence standard, response SLA, security.txt, PGP status. Where SU.04 routes to.
Data should be minimal, not theatrical
UK GDPR-aligned privacy notice. Controller, data map, lawful basis, retention, processors, rights. The privacy lane on this page.
The assistant does not improvise authority
Bounded corpus, refusal protocol, AI input boundary. Where the SU.03 “limited” state originates.
Use the site. Do not rely on it
Website and preview terms. Where the “not an SLA” rule from sheet 05 traces back to.
The holding entity, the legal wall, the public surface
BlackMenta Ltd · № 16988667 · the public cover sheet for the IP holding entity behind these surfaces.
Notes.
- N.01 Signal, not promise. Each row reports a state at the last verified review, not a continuous guarantee. Status pages that conflate the two are marketing pages. → see Sheet 03 · legend
- N.02 Human review. Updates are written human-reviewed, not auto-generated. The cadence is irregular by design; stale dates are themselves a status signal. → see Sheet 07 · chronology
- N.03 Severity adjusts targets. Security incidents on a green surface are fast-tracked. Cosmetic issues on a pending surface are queued. The Sheet 06 windows are the middle band. → see Sheet 06 · severity rule
- N.04 Draft status. This is a public status surface in preview-phase form. Final wording, surface coverage and incident protocol are reviewed by counsel before final publication. → see signature block
- N.05 Status corrections: hello@blackmenta.com. Suspected security or data issue: security@blackmenta.com.