What's New

Recent changes at AstroSpider — new capabilities, new pages, and what is currently being built. Dated, so you can tell how current it is.

Current as of October 22, 2026

  1. Ask out loud: push-to-talk voice

    Super Spider Bot can now take a spoken question. Hold the microphone button beside Send, ask, and let go. A spoken question gets a shorter answer, read aloud by a voice on your own device.

    The microphone records only while the button is held. The audio is turned into text on the cloud platform the assistant already runs on, and the question is then answered like a typed one; the assistant keeps neither the audio nor a transcript of it. Voice is switched on per deployment, and that assistant’s terms say so before any audio is sent. The Spider Bot on this site answers in text. See Atlas for the Spider Bot family.

  2. Beyond RAG, and a new top tier

    The Applied AI page now sets out how we choose the way an assistant gets its knowledge for each kind of question: prepared facts for answers that must be exact, context engineering, retrieval that earns its place, and agentic reading for questions that need a whole document. Retrieval-augmented generation is one of those patterns, not the default.

    Ultra Spider Bot, the top of the Spider Bot family, is redefined to match. Instead of “full RAG”, it is the full router: one governed design that picks the right path for each question, with an evaluation suite that proves each change. Super Spider Bot can now also answer exact questions from prepared, checked facts. See Atlas.

  3. Inside AstroSpider

    A new page at Inside AstroSpider covering how the company works internally — a repository-first environment across every discipline rather than engineering alone, and onboarding that assumes no prior Git experience and teaches the process instead.

    It also carries the standard AstroSpider holds its own claims to: every assertion labelled with how it is known, from untested intuition through to a result with a method behind it. The page applies that to itself, including a section on what we are currently curious about in AI memory that says plainly these are open questions and not published results.

  4. Direct scheduling on real calendar availability

    AstroSpider now has its own booking page at /book. It reads live availability straight from the calendar rather than collecting a request and replying later — pick a service, pick a time, and the appointment is confirmed on the spot.

    It is a custom front end built on the Microsoft Graph bookings API, which means the business rules around lead time, duration, and buffers are enforced in our own code rather than inherited from a hosted booking page.

  5. Direct scheduling for recruiters

    Recruiters and staffing partners get their own scheduling link with a shorter lead time, so those conversations do not compete with client work for the same slots.

  6. AI Ready, and the readiness framework behind it

    AI Ready lays out what it actually takes for an organization's knowledge to be usable by AI: source authority, validation, metadata, retrieval design, grounding and citations, abstention rules, evaluation, and operational monitoring.

    It also documents the seven-stage AstroSpider AI Readiness Framework — Discover, Classify, Validate, Structure, Retrieve, Evaluate, Operate — and takes a clear position on meeting transcripts, which are among the most useful and most dangerous sources you can put in a knowledge system.

  7. The Spider Bot family became a three-tier ladder

    AI assistant offerings were reframed from two options into three, delivered by Atlas Labs on the Atlas™ framework: Spider Bot (curated knowledge), Super Spider Bot (curated core plus targeted retrieval), and Ultra Spider Bot (full RAG with document ingestion and role-based access).

    The reason for a middle tier is that most organizations do not need full retrieval infrastructure, and the jump from curated to full RAG was too large a step to be the only option on offer.

  8. Spider Bot remembers across visits

    Spider Bot gained a per-visitor memory layer, so a returning visitor does not start from scratch. Conversations are folded into a rolling summary keyed to an anonymous identifier — no account, no email required.

    It is deliberately conservative: the summary is allowed to record that no specifics were shared, because a memory layer that invents plausible detail is worse than one that admits it does not know.

  9. The interactive technology web

    Our Web became an interactive map of the technologies AstroSpider works across, with the spider drawing its own strands out to each node. The artwork is hand-drawn in Inkscape, not generated.

In Development

  • Hybrid retrieval for Super Spider Bot. Sparse keyword search for exact codes and identifiers, dense embeddings for meaning, and cross-encoder reranking so the governing rule reaches the top of the context rather than merely appearing in it. A knowledge graph layer is under evaluation, not assumed.
  • Role-grounded corpus design. Building assistants around what a specific operational role needs to know, rather than around a subject area. Medical billing and revenue-cycle operations is the reference domain, chosen because exact-match codes, conflicting payer policy, and real financial consequences make it a genuinely hard case.

Want to talk about any of it?

Pick a time that works. Real calendar availability, confirmed immediately, no cost and no obligation.

Book a Conversation