1sealsemantic last-mile verification

archive · not the current model

Pages from an earlier 1seal.

The site previously described a different product model — SealGuard, PoisonAtlas, an agent-security product line, a services catalogue. Those pages are kept where they are still useful as reference, and marked so that no reader mistakes them for the current one.

archived

Anything under this section describes a superseded model. Claims, names and roadmaps there were not re-reviewed. The current model is last-mile verification: the gap, how it works, status.

A.1

What happened to each page

One decision per page, taken once, recorded here. Three outcomes only: rewrite into the current model, archive with the banner above, remove with a redirect to the nearest current page.

pagedecisionwhere it goes
/problemrewrittencurrent — the gap
/protocolsrewrittencurrent — protocols
/researchrewrittencurrent — research
/statusrewrittencurrent — status
/domainsrewrittenfolded into protocols §4.5 · redirect /domains → /protocols#domains
/productsremove + redirect→ /status · product names belonged to the old model
/use-casesremove + redirect→ /problem · the five exploitation patterns replace it
/integrationsremove + redirect→ /status · integrations imply availability that does not exist yet
/threatsretirement noticeunsupported deployment claims removed; current problem and status
/labsretirement noticeunsupported availability claims removed; current research and services
/rc, /schemasarchivedhistorical technical references, not current contracts
/playgroundkeep, secondaryrequired-field demo only; no signature verification
/servicesrewritten, secondarycurrent — services · footer only, boundary stated on the page
/behind-the-workrewritten, secondarycurrent — behind the work · footer only
/security-policykeep, secondaryshared presentation; policy text preserved
/research/policykeep, secondaryshared presentation; policy text preserved

Archived pages carry a banner and are excluded from the current sitemap. A visual refresh does not revalidate historical claims.

A.2

Rules for archived pages

  • bannerthe archive bar is the first element inside <main>, before the h1
  • navsame header and footer as current pages — one site, one navigation
  • stylesthis stylesheet only; brand.css and main.css are removed from the page
  • claimsunsupported claims may be replaced by an explicit retirement notice; archival presentation does not validate them
  • indexingnoindex, and no links from current pages except this list