Speconaut

Docs

Project notes for a future assistant

Speconaut is a concept with real infrastructure. These notes keep the intention visible while the actual assistant continues to mature inside specifications.global.

Current State

Live

The static Speconaut website, domain, SSL, CloudFront, S3 origin, docs, draft API page, and login placeholder are live.

Demo

The assistant-like behavior remains on specifications.global, where product pages and raw text already exist.

Not live

No public Speconaut API, SMS provider, account backend, billing, or partner dashboard is connected yet.

Principles

  1. Answer from product memory. Speconaut should prefer known product pages, raw text, and source traces over generic guesses.
  2. Keep context alive. Follow-up questions should remain anchored to the same products unless the user changes the subject.
  3. Say when it is early. The service should clearly disclose missing sources, weak comparisons, and unavailable features.
  4. Sound like itself. The goal is a practical, product-focused assistant with a consistent way of explaining tradeoffs.

Raw Text Strategy

Raw text is the early memory layer. It can include product descriptions, manual notes, scraped source excerpts, model identifiers, review summaries, and observed answers from the current demo.

Input Purpose Status
Product pages Canonical model and variant identity Active on specifications.global
Raw text Retrieval memory and answer grounding Growing
Conversation examples Prompt behavior and follow-up continuity Demo phase
Retail context Future in-store guidance Planned

Roadmap

Now Static identity and SEO base

Keep the domain useful, document the intent, and point back to the working demo.

Next Retrieval and session continuity

Improve product pair memory, follow-up handling, source selection, and raw text coverage.

Later Accounts and API

Add authentication, SMS verification, API keys, session storage, and partner clients.

Future Storefront assistant

Explore an assistant that can guide real customers through real product choices.

Boundaries

Speconaut should not claim full product coverage, expert certainty, or working account/API access until those systems exist. The site should make the project legible without over-selling it.