This index exposes the material behind every decision guide: what we reviewed, when we retrieved it, the claim it supports and where the evidence stops.
181decision guides
790source records
782scoped claim notes
How to read this index
A citation is not a transferable result.
Reviewed identifies the part of the source used. Supports states the bounded proposition we draw from it. Retrieved records when time-sensitive material was checked.
Vendor documentation establishes vendor claims and product behavior as documented, not independent performance. Papers establish results only for their stated methods and tested scope. AccessAllGPT recommendations remain labeled analysis.
AccessAllGPT reviewed five first-party surfaces on November 5, 2026: Moonshot’s launch article, the Kimi API quickstart and pricing table, the official Hugging Face repository/model card and the repository license. We checked the public-repository timestamp and files, exact model IDs, context and architecture claims, API access and request constraints, token prices, vendor benchmark methodology notes and commercial-license conditions. We also downloaded the README, config and license and validated the config as JSON. Their SHA-256 digests were 5daa13793292c65cf198b2f4997c69a21378a1688c40c8b3dbdf48a27dd15085, d95037631e3f23bf527a9f476f25209b231b46853a84877b9c56d5672b8d1202 and da05c356f773d22a0e1c6de390f280304d7cee6eb56fa161aa789d30dedba63b respectively. Product and benchmark statements are vendor claims; repository presence and metadata are registry facts; deployment guidance is AccessAllGPT analysis. We did not download the 96 weight shards, run the model, call the API, reproduce a benchmark, measure memory or throughput, obtain legal advice, or verify product rollout behind an authenticated account.
Reviewed: Structured metadata; launch overview; availability; coding, 3D and finance claims; cybersecurity release rationale; benchmark footnotes
Supports: Moonshot describes K3.1 Pro and Highspeed, their product and API availability, planned open-weight release, vendor benchmark results and stated open-weight safety rationale. Its structured data carries a 2026-10-24 dateModified value.
Reviewed: Overview; access requirements; model IDs; reasoning effort; streaming; vision; structured output; dynamic tools; context caching; official tools; important limits
Supports: The live API guide documents kimi-k3.1-pro and kimi-k3.1-pro-highspeed, a minimum $1 top-up, always-on thinking, 1M context, vision and tool behavior, fixed sampling settings and current web-search warning.
Reviewed: K3 series model IDs, standard input and output rates, cached-input rates, cache-write rates, automatic cache billing and batch discount
Supports: Kimi lists Pro at $2 input and $10 output per million tokens and Highspeed at $4 input and $20 output, with separate cache prices. Standard Pro supports batch inference at 60% of standard price.
Reviewed: Repository creation record; model introduction; model summary; configuration; evaluation table; files and versions; license identifier
Supports: The public repository was created November 2, 2026 and contains 96 safetensor shards plus configuration and inference code. The model card identifies a 2.8T-parameter, 104B-active multimodal MoE with 1,048,576-token context and vendor-reported evaluations.
Reviewed: Granted rights; notice requirement; Model as a Service definition and revenue threshold; large-product attribution threshold; exemptions; warranty disclaimer
Supports: The custom license permits use, modification, deployment, fine-tuning and distribution, but introduces a separate-agreement condition for qualifying model-as-a-service businesses and an attribution condition for very large commercial products.
AccessAllGPT reviewed five first-party OpenAI surfaces on November 5, 2026: the official OpenAI News RSS record and canonical announcement URL, the complete image-generation developer guide, the live Sunburst and Flare model pages, and the API pricing table. We checked the announcement date and availability language, exact model IDs, intended roles, supported endpoints, request controls, output formats and constraints, documented limitations, safety guidance and token rates. The canonical announcement body returned a Cloudflare challenge, so claims beyond its official RSS summary come only from the accessible developer documentation. Availability and capability statements are vendor documentation; live page and model-card presence are registry facts; rollout guidance is AccessAllGPT analysis. We did not sign in to ChatGPT or Codex, call either API model, generate or edit an image, measure speed or quality, calculate a representative per-image bill, test moderation, or independently compare Sunburst, Flare or GPT Image 2.5.
Reviewed: Official OpenAI News RSS title, summary, Product classification, canonical URL and November 4 publication timestamp; the canonical article returned a Cloudflare challenge during review
Supports: OpenAI announced Images 2.6 on November 4, 2026 and describes faster image generation, GIF creation, more precise editing and new API controls across ChatGPT, Codex and the API. The blocked article body was not used for additional claims.
Supports: OpenAI documents Sunburst and Flare, low/medium/high complexity, markup-guided edits, static SVG and animated GIF generation through the Image API, output constraints, known limitations and token-based cost behavior.
Reviewed: Model identity, intended use, input and output modalities, text and image token prices, supported endpoints, snapshot alias and rate-limit note
Supports: The live model page identifies gpt-image-2.6-sunburst for detailed visual work, lists image generation and edit endpoints as supported, and lists the Images API token rates. Responses API support is marked unavailable on this model page.
Reviewed: Model identity, intended use, input and output modalities, text and image token prices, supported endpoints, snapshot alias and rate-limit note
Supports: The live model page identifies gpt-image-2.6-flare for fast iteration, lists image generation and edit endpoints as supported, and lists the same Images API token rates as Sunburst. Responses API support is marked unavailable.
Reviewed: Standard image-generation pricing table for GPT Image 2.6 Sunburst and Flare; text input, image input, cached input and image output token rates
Supports: OpenAI lists identical standard token rates for both GPT Image 2.6 variants: $5 per million text-input tokens, $1.25 cached; $8 per million image-input tokens, $2 cached; and $30 per million image-output tokens.
AccessAllGPT reviewed four author-controlled or first-party release surfaces on November 4, 2026: Ai2’s complete November 3 briefing, the authors’ November 2 arXiv record and abstract, the public GitHub repository and README, and the Hugging Face dataset page. We checked the release dates, task hierarchy, paired generation method, evaluated model names, headline accuracy claim, direct-training setup, repository commands, dataset availability and stated open questions. All scores, theoretical conclusions and architecture comparisons are author-reported; public artifacts are registry facts; deployment guidance is AccessAllGPT analysis. We did not run the generator, download the dataset, call any evaluated model, reproduce scoring, inspect provider-specific prompts or hidden reasoning, verify inference settings or costs, retrain an architecture, or independently review the mathematical proofs.
Reviewed: November 3 publication date; four-level state-tracking hierarchy; open pretrained-model evaluation; frontier-model evaluation; direct-training experiments; open questions; paper, data and code links
Supports: Ai2 released StateBench on November 3, 2026 and reports that Gemini 3.8 Flash, Claude Opus 5.5, GPT-6 Sol and GPT-6 Luna fall to 13% accuracy or lower on its longest general-finite cases. The post labels the benchmark, data and code as released and describes important scope limits.
Reviewed: November 2 submission record; abstract; four-level hierarchy; transformer and Gated DeltaNet theory; direct-training experiments; pretrained open and closed model evaluation; stated conclusion
Supports: The authors define r-trivial, aperiodic, soluble and general-finite state tracking, present theoretical architecture results and report that none of the evaluated pretrained models robustly solves even soluble state tracking. This is an author paper, not independent replication.
Reviewed: README hierarchy definitions; paired-trace generation; formatters; train/test disjointness; reproducibility commands; long-context schedules; published dataset references; configuration and validation behavior
Supports: The public repository provides code and configuration for generating reproducible linked state-tracking tasks, rendering multiple surface forms and staging the dataset. Its default long-context schedule reaches 64,000 assignments and documents disjoint train and test construction.
Reviewed: Public dataset landing page; dataset identity; available files and viewer surface; relationship to the repository and November 3 release
Supports: Ai2 has made the StateBench dataset publicly accessible on Hugging Face. Availability of files supports reproducibility work but does not independently validate benchmark construction, scoring or the reported model results.
AccessAllGPT reviewed three first-party OpenAI records on October 30, 2026: the official RSS record for the October 29 announcement, the complete dated October 29 Model Spec and the prior September 12, 2025 Spec. We compared the published heading structures and read the new overview, authority levels, oversight, context, harm, honesty, agency, care and under-18 provisions. The announcement page returned a Cloudflare challenge, so claims attributed to that page are limited to its official feed title, timestamp and summary. Specification text is an OpenAI policy statement about intended behavior, not independent evidence of model behavior. AccessAllGPT did not test ChatGPT or the API, compare model outputs, inspect system prompts, validate enforcement, measure refusal or compliance rates, or receive rollout information.
Reviewed: Official RSS publication record, October 29, 2026 publication timestamp, announcement title and summary; the article page itself returned a Cloudflare challenge during review
Supports: OpenAI published the update at 17:00 UTC on October 29. Its official feed says the revised Model Spec is organized around five core values intended to guide capable AI toward sound judgment, human agency and faithfulness to human intent.
Reviewed: Overview; five-value structure; red-line principles; instruction hierarchy; human oversight; context use; harm boundaries; honesty; human agency; teen protections; production-alignment and public-version caveats; CC0 status
Supports: The dated public specification defines five values, reorganizes the behavioral hierarchy and adds explicit principles for oversight, contextual memory use, real-world ties, side effects, capability transparency, agency and users under 18. OpenAI says production models do not yet fully reflect the Spec.
Reviewed: Prior overview and structure; chain of command; scope and side-effect rules; Stay in bounds; Seek the truth together; Do the best work; Use appropriate style; prior teen-safety and context-treatment coverage
Supports: The prior dated version organized instructions under the chain of command, Stay in bounds, Seek the truth together, Do the best work and Use appropriate style. Comparing its published headings with the October 29 version establishes the structural changes without implying that every wording change is new product behavior.
AccessAllGPT reviewed five public surfaces on October 30, 2026: Mistral’s complete October 29 release announcement, the live Mistral model documentation, the public Hugging Face model repository and model card at commit f12dabdc0c1e99e7f7924461a6f308859b05af4d, the license text, and Hugging Face’s launch and integration article. We checked model and API identifiers, availability, architecture, context, modalities, reasoning modes, pricing, artifact formats, serving routes, license conditions, benchmark descriptions and disclosed limitations. Repository access, files, documentation and displayed prices are directly observable. Performance, safety, training and token-efficiency results are vendor or evaluation-provider claims. AccessAllGPT did not download the roughly trillion-parameter checkpoint, run inference, call the API, reproduce benchmarks, validate the training lineage, inspect training data, or obtain the specialized cybersecurity variant.
Reviewed: October 29, 2026 publication metadata; weight release and availability; coding, cyber, finance, browsing and agent-security claims; reasoning modes; managed and self-hosted routes; API pricing; license summary; technical-report status
Supports: Mistral announced the improved Mistral Large 4 weights on October 29, described three reasoning modes and multiple deployment routes, published API pricing, and reported benchmark and safety results. The page says a full technical report is still forthcoming.
Reviewed: Model version and public-preview label; API aliases; 1M context; input, cached-input and output prices; supported modalities; structured output, function calling, document Q&A, batching, agents and built-in-tool endpoints
Supports: The live documentation lists Mistral Large 4 version 26.10, aliases mistral-large-4 and mistral-large-4-0, a one-million-token context window, text and image input with text output, and API prices of $0.70 input, $0.07 cached input and $2.10 output per million tokens.
Reviewed: Public ungated repository at commit f12dabdc0c1e99e7f7924461a6f308859b05af4d; model identity; architecture and active parameters; training-compute statement; modalities; languages; 1M context; tool and JSON support; FP8 files; inference-engine support; benchmark methodology notes
Supports: The public ungated repository exposes 54 FP8 safetensor shards at the reviewed commit. Its model card describes a one-trillion-parameter multimodal mixture-of-experts model with 49 billion active parameters per token, 128 routed experts with four active plus one shared expert, and support for Transformers, vLLM, SGLang and llama.cpp.
Reviewed: License text at repository commit f12dabdc0c1e99e7f7924461a6f308859b05af4d; use, copy, modification, distribution, sublicensing and sale grant; attribution condition; Model-as-a-Service commercial-license condition; warranty and liability terms
Supports: The modified MIT-style license permits broad use, modification, distribution and commercialization, but requires a separate Mistral commercial license when the licensee or an affiliate operates a Model-as-a-Service business and uses the model or derivatives commercially.
Reviewed: October 29, 2026 publication date; FP8 and NVFP4 official variants; community GGUFs; architecture overview; benchmark discussion; Transformers, vLLM and llama.cpp support; fine-tuning and Inference Endpoints sections
Supports: Hugging Face independently confirms that the weights are published in official FP8 and NVFP4 variants, describes community GGUF conversions, and documents current inference and fine-tuning integration paths. It does not provide an independent benchmark reproduction.
AccessAllGPT reviewed four first-party Google surfaces on October 30, 2026: the complete October 29 launch announcement, the current Gemini Canvas help page, the file-upload help page and the Gemini Apps Privacy Hub updated October 26. We recorded the announcement date, formats, platform boundaries, editing modes, availability language, sign-in requirement, administrator dependency, paid-plan limit wording and documented data-control topics. Product capabilities and availability are Google statements. AccessAllGPT did not sign in, upload or generate a file, edit a PDF, test web or mobile behavior, compare plans, exhaust a quota, validate formatting fidelity, measure latency or accuracy, inspect enterprise controls, or audit privacy and accessibility behavior.
Reviewed: October 29, 2026 announcement date; supported file categories; direct and AI-assisted editing; web and mobile availability boundary; all-user and language availability statement; PDF study-guide example
Supports: Google announced that Gemini can generate, preview and edit documents, PDFs, presentations, spreadsheets, Markdown, text and code inside a chat. PDF preview and editing are available on web and mobile; the other named formats are web-only. Google says the capabilities are available to all users in every language where the Gemini app is available.
Reviewed: Sign-in requirement; Canvas entry flow; direct and prompt-based document editing; autosave behavior; selection editing; text formatting; creation and export controls; age boundary for derivative creation
Supports: The live help page requires a Gemini Apps sign-in and documents direct text editing, prompt-based edits, selection edits, formatting and autosave in Canvas. It also says some creation features based on a Canvas document are not available to users under 18.
Reviewed: Sign-in requirement; device, Google Drive, code-folder and GitHub inputs; organization-admin requirement for work or school Drive files; higher-limit plan language; file types and upload-limit section
Supports: Google documents file uploads from devices and Drive, plus code-folder and GitHub inputs. Work and school Drive access can depend on an administrator, and Google advertises higher file limits on paid AI plans; the page does not establish unlimited use for the newly announced editor.
Reviewed: October 26, 2026 update date; Gemini Apps Privacy Notice; information provided to Gemini; service-improvement and human-review explanations; Keep Activity and retention controls; uploads; Canvas data and safety sections
Supports: Google’s current Privacy Hub describes data collection, service-improvement and human-review considerations, activity and retention controls, uploads, and Canvas-specific data and safety topics. Organizations should apply those terms to the files they intend to edit rather than infer a private document-processing mode from the product announcement.
AccessAllGPT reviewed two first-party Google surfaces on October 29, 2026: the complete October 28 Gemini 4 Carbon announcement and Google DeepMind’s live Fairwind Program page. We checked the announcement date, current and promised access, intended token prices, named capability areas, benchmark figures, evaluation qualifications, safety claims and staged-rollout language, then cross-checked the public early-access program’s eligibility and governance description. Announcement text and public program terms are directly observable; performance and safety results are Google-reported. AccessAllGPT did not receive Carbon access, invoke an API, obtain a model ID, reproduce a benchmark, inspect the underlying evaluation logs or verify a general product rollout.
Reviewed: October 28, 2026 announcement date; staged availability; intended pricing; coding, agentic and cyber positioning; vendor benchmark results; safety claims; rollout language
Supports: Google announced Gemini 4 Carbon on October 28, 2026. It says access starts this week for a subset of cyber defenders, broader developer and consumer access is coming later, intended launch pricing is $2 per million input tokens and $10 per million output tokens, and cached input is intended to be 95% cheaper than input.
Reviewed: Program purpose; partner count; eligibility; governance; managed-access restrictions; permitted dual-use tasks; technology description; application and FAQ sections
Supports: Google DeepMind describes Fairwind as a vetted early-access program for defensive and academic cyber work, says it works with more than 650 partners, and documents restricted access, due diligence, user authentication and defensive-use conditions. The page still named Gemini 4 Argon rather than Carbon when reviewed.
AccessAllGPT reviewed four public surfaces on October 29, 2026: the complete Hugging Face launch article, both GitHub repositories and READMEs, their current tags and commits, package licenses, and representative Parakeet and Qwen3-ASR Core ML artifact records on the Hugging Face Hub. We checked the publication date, installable versions, immutable commits, backend matrix, model routes, platform requirements, documented download and memory estimates, package-authored evaluation setup, probability semantics, known incompatibilities, license labels and artifact access. Repository state, tags and public artifact metadata are directly observable. Accuracy, speed, memory, calibration and conversion-equivalence results are author claims. AccessAllGPT did not build either Swift package, download model assets, run speech or decision inference, reproduce an evaluation, use Jev or Ollama, or test an iPhone.
Reviewed: October 29, 2026 publication date; package scope; supported speech and decision backends; Core ML artifact matrix; download sizes; author-reported evaluations; platform requirements; installation versions; current incompatibility note
Supports: Hugging Face published the launch on October 29. The author presents AnySpeechRecognizer 0.1.0 and AnyDecisionModel 0.6.0 as Swift packages for replaceable on-device speech engines and typed probabilistic decisions, and documents requirements, model routes, benchmark results and limitations.
Reviewed: 0.1.0 tag and commit fd305213a4ceb6b89bc417f09338b0ab92e60ede; API compatibility; requirements; Apple, Parakeet and Qwen3-ASR capability matrix; pinned asset verification; memory and download estimates; diarization; evaluation methodology; Apache-2.0 package license
Supports: The public repository exposes a 0.1.0 tag at commit fd305213a4ceb6b89bc417f09338b0ab92e60ede. Its README documents Apple, Parakeet and Qwen3-ASR routes, platform and hardware limits, pinned-file verification, package-authored evaluations, known gaps and an Apache-2.0 software license.
Reviewed: 0.6.0 tag and commit 66b2fe218989c26e53267b91271278256863f8a7; typed decision API; six backends; platform requirements; probability, confidence and calibration semantics; choice limits; dependency traits; test scope; limitations; Apache-2.0 package license
Supports: The public repository exposes a 0.6.0 tag at commit 66b2fe218989c26e53267b91271278256863f8a7. It documents six backends, local and hosted execution, typed probability outputs, calibration controls, backend-specific constraints and explicit limitations including fixture-only Jev and Ollama wire testing.
Reviewed: Public and ungated repository state; base-model relation; model commit f2f43eaa239d1ea45191c2a2d5bd0f980dae1b1f; CC BY 4.0 metadata; Qwen3-ASR 1.7B Core ML record at commit 63bece09d5ec2a8d47cdf3227b8dcf5aa00ecefa; Apache-2.0 metadata; inference-provider availability
Supports: The reviewed Parakeet and Qwen3-ASR Core ML repositories were public and ungated. Hub metadata linked each conversion to its base model and license; the Parakeet page stated that no Hugging Face Inference Provider deployed that conversion when retrieved.
AccessAllGPT reviewed four public sources on October 29, 2026: Anthropic’s complete October 27 research report, Google’s Chrome 156 stable-channel security release, the NIST NVD record for CVE-2026-33096 and Anthropic’s October 6 Cyber Verification Program announcement. We recorded what Anthropic attributes to the unreleased research model, which findings have external identifiers or vendor release evidence, what access is available now, and which experimental details remain undisclosed. We intentionally omit reproduction steps and operational exploit detail. The five-chain result, Chrome CVE totals, scanner contribution and model-capability conclusions are Anthropic claims unless separately identified. AccessAllGPT did not receive model access, source code, prompts, trajectories, proof-of-concept files, the complete vulnerability list, vendor correspondence or raw scanner results; did not run an exploit or scan; and did not contact affected vendors.
Reviewed: October 27, 2026 publication date; unreleased-model disclosure; five reported attack-chain case studies; coordinated disclosure statement; Chrome CVE totals; patch status; scanning method; limitations stated through the article; defender guidance
Supports: Anthropic says an unreleased internal research model helped produce five multi-stage exploit chains affecting Chrome, Safari, Android, Windows and Linux. It reports coordinated disclosure, vendor fixes or upstream patches, 62 assigned Chrome CVEs, parallel scanner diversity, standardized verification, and no public identity or access route for the research model.
Reviewed: October 20, 2026 release date; Chrome 156 stable versions; security-fix count; critical and high-severity entries; reporter and Claude-assistance attributions; restricted bug-detail notice
Supports: Google’s Chrome 156 release record says the update includes 353 security fixes, lists critical and high-severity vulnerabilities, credits multiple Anthropic researchers and some Claude-assisted reports, and warns that bug details may remain restricted until most users receive fixes.
Reviewed: CVE identifier; publication and modification timestamps; English description; CVSS 3.1 vector and score; Microsoft vendor-advisory reference; CISA SSVC fields
Supports: The NVD record describes an out-of-bounds read in Windows HTTP.sys that permits unauthenticated network denial of service. Microsoft’s supplied CVSS 3.1 vector is network reachable with no privileges or user interaction and carries a 7.5 High base score.
Reviewed: October 6, 2026 announcement; Defense, Red Team and Specialized access tiers; eligibility and review timing; model names; safeguards; retention boundary; platform availability; application process; CyScenarioBench vendor evaluation
Supports: Anthropic says qualifying security professionals can apply for tiered access to named production models and reduced blocking classifiers. CVP is available through Claude Platform, Vertex AI and Microsoft Foundry, with conditional Bedrock access; the page publishes no price and does not identify the unreleased model used in the five case studies.
AccessAllGPT reviewed five first-party Google surfaces on October 29, 2026: the complete October 28 launch announcement, the platform overview, the remote MCP developer guide, the OAuth implementation guide and the consumer Gemini Connected Apps help page. We recorded the announcement date, current and promised product surfaces, integration paths, onboarding and review steps, authorization requirements, observable user controls, partner rollout, pricing omissions and unresolved availability terms. Product descriptions and documentation are Google statements. AccessAllGPT did not receive preview access, sign in to Connected Console or Gemini, register an app, deploy an MCP server, implement AppFunctions or OAuth, submit an integration for review, invoke a partner app, measure telemetry, verify Search rollout or obtain private commercial terms.
Reviewed: October 28, 2026 announcement date; preview availability; Gemini and Search surfaces; integration paths; Connected Console workflow; telemetry; partner rollout; pricing and market omissions
Supports: Google announced the Connected Apps Platform preview on October 28, 2026. It describes remote MCP and Android AppFunctions integration paths, Connected Console registration and review, phased developer access, more than 50 Connected Apps across Gemini and Search, currently live Gemini partners, and Search expansion in the coming weeks.
Reviewed: Platform overview; user linking and action model; remote MCP server path; Android AppFunctions path; Connected Console registration; preview application status
Supports: Google’s developer overview says Connected Apps can use authorized account context and complete actions in applicable Google products. It identifies remote MCP and Android AppFunctions as the integration paths and says preview onboarding is self-service through Connected Console after developers apply for access.
Reviewed: Developer benefits; invocation behavior; MCP and Android integration options; build, validate, developer-mode test and Connected Console registration phases; safety and schema guidance
Supports: Google documents remote MCP as the default cross-platform route, Android MCP as the client-side route, explicit app invocation by name, and a four-phase workflow from server development through local validation, Gemini Developer mode and Connected Console registration.
Supports: Google recommends OAuth 2.1 delegated authorization for Connected Apps MCP integrations, requires PKCE for OAuth 2.1, supports authorization code with PKCE, and requires authorization-server metadata discovery for automatic onboarding.
Reviewed: Permission and action description; personal-account scope; sign-in and Keep Activity prerequisites; connect and disconnect controls; supported-action discovery; Google Messages limitation
Supports: Google says Gemini can use connected apps with permission to answer requests and take actions, personal users must be signed in and should check Keep Activity, connections can be managed in settings, and Connected Apps are not currently available inside Gemini in Google Messages.