The concept tree

Every concept the hub has researched, under the roots it hangs from. A frontier name is one some node lists as a child but which has no node of its own: this site derives it from the tree's childConcepts on every build, never stored as a status. The hub counts a second source we do not publish — the unchecked rows of its research queue, which is not snapshotted here — so this count is the tree's alone. How to read this.

37 researched · 0 frontier · generated 2026-08-30 · 3D view

Filter

• Adult and Membership Ecommerce
  • Adult Ecommerce Operations
  • Adult Product Distribution and Dropship Sourcing
  • Members-Only and Wholesale Pricing
  • Squarespace Commerce and Payments
  • Membership Site Architecture
  • Membership Platforms Build vs Buy
  • High-Risk Payments and Chargeback Management
  • Ecommerce Sales-Tax Nexus Compliance
• Cross-Browser and Mobile Web Programming
  • Cross-Browser Extension and Userscript Portability
  • Browser Engine Differences and Feature Detection
  • Cross-Browser Testing and Debugging
  • Mobile-Web and Browser Security Differences
  • Web-to-Native App Packaging
• Global Context Hub Architecture
  • Concept Tree Tracking
    • 3D Force-Directed Graphs
  • Library Registries
    • MCP Server Library
    • Repo Scenarios Library
    • URL Reference Library
    • Shared Code Library
  • Execution and Telemetry
    • File Analysis and Logs
    • Agent and Role Bindings
    • Aider Persistent Memory Hooks
    • Stdlib-Only Python Architecture
  • Code and Prompts
    • Reusable Coding Patterns
    • Prompt Optimization and Variants
• llms.txt and LLM-readable documentation
  • llms.txt specification v2
  • llms-full.txt page grammars
  • llms.txt generation tooling
  • llms.txt ecosystem evidence
  • llms.txt recreation and family aggregation