fix(docs): align docs site with launch playbook four-layer framing

Rewrite docs homepage hero to mirror aster.site: eyebrow now says
'Peer-to-peer RPC framework', tagline is the durable thesis, lead
paragraph rolls in the pain catalog + 'identity in the connection'
line, and the hero metrics strip now names iroh, Apache Fory,
BLAKE3, and four-gate auth instead of generic labels.

Primary CTA is 'Build Mission Control' matching aster.site; secondary
is 'Try it in 60 seconds'. Kills the broken TypeScript CTA and the
gRPC-killer framing from the hero. Launchpad and language strip
language cards now link to the right destinations. 'AI-native'
section kicker reframed as 'MCP integration' per playbook vocabulary.

Overview docs: what-is-aster.mdx and why-aster.mdx both now open
with the durable thesis and 2026 agent example before any mention
of identity-first framing or gRPC comparisons.

Quickstart sidebar order: python quickstart, Mission Control
walkthrough, then What's next. sidebar_label overrides make the
progression explicit.

Config: tagline + footer + navbar GitHub link all point at the
repo instead of the org and match the aster.site durable phrase.

Author: emrul

.docusaurus/docusaurus.config.mjs

@@ -5,7 +5,7 @@
  */
 export default {
   "title": "Aster",
-  "tagline": "RPC after hostnames.",
+  "tagline": "Machines authenticate to machines, on behalf of users.",
   "favicon": "img/favicon.ico",
   "future": {
     "v4": {
@@ -116,7 +116,7 @@ export default {
           "position": "left"
         },
         {
-          "href": "https://github.com/aster-rpc",
+          "href": "https://github.com/aster-rpc/aster-rpc",
           "label": "GitHub",
           "position": "right"
         }
@@ -148,7 +148,7 @@ export default {
           "items": [
             {
               "label": "GitHub",
-              "href": "https://github.com/aster-rpc"
+              "href": "https://github.com/aster-rpc/aster-rpc"
             }
           ]
         }

docs/overview/what-is-aster.mdx

@@ -4,13 +4,15 @@ title: What is Aster?
 slug: /overview/what-is-aster
 ---
 
-Aster is an identity-first RPC framework for distributed systems. It replaces the hostname-and-infrastructure model of conventional RPC with cryptographic identity, peer-to-peer transport, and content-addressed service contracts.
+**Aster is a peer-to-peer RPC framework. Machines need to authenticate to other machines, often on behalf of a user, and Aster makes that safe — without a central authority and without shared secrets.**
+
+The 2026 vivid example is AI agents calling tools on remote machines: an agent on machine A wants to invoke a function on machine B, you don't want a hosted proxy in between, you don't want to rotate API keys, and you want the call to be scoped to specific methods. That's exactly what Aster solves. The same engineering also covers IoT fleets, edge compute, multi-tenant microservices, and anything else where the machine is the principal and the user is the delegating authority.
 
 ## The core idea
 
 In traditional RPC, a service call goes to a network address: a hostname, a port, a load balancer. The identity of the thing you are talking to is an afterthought, bolted on via TLS certificates or OAuth tokens.
 
-Aster inverts this. Every endpoint has an ed25519 keypair. The public key *is* the address. When you dial a service, you dial a cryptographic identity -- not a hostname, not an IP address, not a DNS record. The underlying transport resolves that identity to a network path, handles NAT traversal, and establishes an end-to-end encrypted QUIC connection. No infrastructure required.
+Aster inverts this. Every endpoint has an ed25519 keypair. The public key *is* the address. When you dial a service, you dial a cryptographic identity -- not a hostname, not an IP address, not a DNS record. The underlying transport resolves that identity to a network path, handles NAT traversal, and establishes an end-to-end encrypted QUIC connection. No infrastructure required. Identity is in the connection, not bolted on.
 
 ## Three independent layers
 

docs/overview/why-aster.mdx

@@ -4,7 +4,15 @@ title: Why Aster?
 slug: /overview/why-aster
 ---
 
-## The assumptions are breaking down
+## The durable problem
+
+**Machines need to authenticate to other machines, often on behalf of a user.** More code now runs on more machines than people, and the gap is widening. Today the answer to machine-to-machine authentication is API keys, mTLS certificates, IAM roles, service mesh sidecars, or OAuth proxies -- five different mechanisms, none of them designed for machines, all of them bolted onto transport that doesn't care about identity.
+
+Aster's answer is to put identity *in* the connection. Every endpoint has an ed25519 keypair, the QUIC handshake authenticates both sides cryptographically, and a four-gate authorization model enforces capability-based access before your code runs. No shared secrets, no central authority, no OAuth proxy in the middle.
+
+The 2026 vivid example is AI agents: an agent on machine A wants to call a tool on machine B without a hosted proxy, without rotating API keys, with access scoped to specific methods. The same engineering covers IoT fleets, edge compute, multi-tenant microservices, and anything else where the machine is the principal and the user is the delegating authority.
+
+## The cloud-native assumptions are breaking down
 
 gRPC, Thrift, and the broader cloud-native RPC ecosystem were built on a set of assumptions that made sense for data-center services behind load balancers:
 

docs/quickstart/first-service.mdx

@@ -1,8 +1,9 @@
 ---
 id: first-service
 title: "What's next"
+sidebar_label: "What's next"
 slug: /quickstart/first-service
-sidebar_position: 2
+sidebar_position: 3
 description: After the quickstart — explore your service, connect AI agents, and prepare for production.
 ---
 

docs/quickstart/mission-control.mdx

@@ -1,6 +1,7 @@
 ---
 id: mission-control
 title: "Build a Control Plane"
+sidebar_label: "Mission Control walkthrough"
 slug: /quickstart/mission-control
 sidebar_position: 2
 description: "Build a real-world control plane with four RPC patterns, session-scoped agents, capability-based auth, and cross-language interop — in under an hour."

docs/quickstart/python.mdx

@@ -1,6 +1,7 @@
 ---
 id: python
 title: Quickstart
+sidebar_label: "60-second quickstart"
 slug: /quickstart/python
 sidebar_position: 1
 description: Get a working Aster RPC service running in under two minutes.

docusaurus.config.ts

@@ -6,7 +6,7 @@ import type * as Preset from '@docusaurus/preset-classic';
 
 const config: Config = {
   title: 'Aster',
-  tagline: 'RPC after hostnames.',
+  tagline: 'Machines authenticate to machines, on behalf of users.',
   favicon: 'img/favicon.ico',
 
   // Future flags, see https://docusaurus.io/docs/api/docusaurus-config#future
@@ -85,7 +85,7 @@ const config: Config = {
         {to: '/docs/quickstart/python', label: 'Quickstart', position: 'left'},
         {to: '/docs/concepts/transport', label: 'Concepts', position: 'left'},
         {
-          href: 'https://github.com/aster-rpc',
+          href: 'https://github.com/aster-rpc/aster-rpc',
           label: 'GitHub',
           position: 'right',
         },
@@ -105,7 +105,7 @@ const config: Config = {
         {
           title: 'Project',
           items: [
-            {label: 'GitHub', href: 'https://github.com/aster-rpc'},
+            {label: 'GitHub', href: 'https://github.com/aster-rpc/aster-rpc'},
           ],
         },
       ],

sidebars.ts

@@ -16,8 +16,8 @@ const sidebars: SidebarsConfig = {
       label: 'Quickstart',
       items: [
         'quickstart/python',
-        'quickstart/first-service',
         'quickstart/mission-control',
+        'quickstart/first-service',
       ],
     },
     {

src/pages/index.tsx

@@ -48,14 +48,15 @@ const POSITION_BY_ID = Object.fromEntries(
 );
 
 const HERO_METRICS = [
-  { label: 'Identity-first transport', value: 'No hostnames required' },
-  { label: 'Typed schemas', value: 'Content-addressed artifacts' },
-  { label: 'Tooling', value: 'Shell + MCP in one runtime' },
+  { label: 'iroh', value: 'QUIC + NAT traversal' },
+  { label: 'Apache Fory', value: 'Cross-language wire format' },
+  { label: 'BLAKE3', value: 'Content-addressed contracts' },
+  { label: 'Four-gate auth', value: 'Offline root key' },
 ];
 
 const LANGUAGE_SUPPORT = [
-  { id: 'python', label: 'Python', state: 'shipping', href: '/docs/quickstart/python' },
-  { id: 'typescript', label: 'TypeScript', state: 'shipping', href: '/docs/quickstart/python' },
+  { id: 'python', label: 'Python', state: 'shipping', href: '/docs/bindings/python' },
+  { id: 'typescript', label: 'TypeScript', state: 'shipping', href: '/docs/bindings/typescript' },
   { id: 'golang', label: 'Go', state: 'in-progress' },
   { id: 'java', label: 'Java', state: 'in-progress' },
   { id: 'kotlin', label: 'Kotlin', state: 'in-progress' },
@@ -361,32 +362,32 @@ function LanguageSupportStrip() {
 export default function Home(): React.JSX.Element {
   return (
     <Layout
-      title="RPC after hostnames."
-      description="Identity-first connectivity, content-addressed service schemas, and cross-language services for real distributed systems.">
+      title="Machines authenticate to machines, on behalf of users."
+      description="Peer-to-peer RPC framework with identity in the connection. Capability-based auth, cross-language wire format, built on iroh QUIC.">
       <main className="asterHome">
         <section className="asterHero">
           <div className="container asterHero__container">
             <div className="asterHero__content">
-              <div className="asterEyebrow">IDENTITY-FIRST DISTRIBUTED SYSTEMS SUBSTRATE</div>
+              <div className="asterEyebrow">PEER-TO-PEER RPC FRAMEWORK</div>
               <h1>Aster</h1>
-              <p className="asterHero__tagline">RPC after hostnames.</p>
+              <p className="asterHero__tagline">Machines authenticate to machines, on behalf of users.</p>
               <p className="asterHero__lead">
-                A transport and typed schema layer for systems that move across peers,
-                runtimes, and trust boundaries before DNS ever helps.
+                Safely &mdash; without a central authority and without shared secrets.
+                No DNS, no load balancer, no certificate authority, no OAuth proxy
+                in the middle. Identity is in the connection, not bolted on.
               </p>
               <p className="asterHero__sublead">
-                Build services once, dial by identity, and expose typed tools to
-                shells, agents, and cross-language clients without a generation maze.
+                The 2026 example: AI agents calling tools on remote machines without
+                a hosted proxy or shared secrets. The same engineering covers IoT
+                fleets, edge compute, and multi-tenant microservices &mdash; anywhere
+                a machine is the principal and the user is the delegating authority.
               </p>
               <div className="asterHero__actions">
-                <Link className="button button--primary button--lg" to="/docs/quickstart/python">
-                  Start with Python
-                </Link>
-                <Link className="button button--primary button--lg" to="/docs/quickstart/python">
-                  Start with TypeScript
+                <Link className="button button--primary button--lg" to="/docs/quickstart/mission-control">
+                  Build Mission Control
                 </Link>
-                <Link className="button button--secondary button--lg" to="/docs/overview/aster-vs-grpc">
-                  Aster vs gRPC
+                <Link className="button button--secondary button--lg" to="/docs/quickstart/python">
+                  Try it in 60 seconds
                 </Link>
               </div>
 
@@ -413,8 +414,8 @@ export default function Home(): React.JSX.Element {
                 and intent still need to hold.
               </p>
               <div className="asterProof__links">
+                <Link to="/docs/quickstart/mission-control">Mission Control walkthrough</Link>
                 <Link to="/docs/overview/why-aster">Why Aster</Link>
-                <Link to="/docs/concepts/transport">Transport model</Link>
                 <Link to="/docs/guides/mcp-integration">MCP integration</Link>
               </div>
             </div>
@@ -468,7 +469,7 @@ producer:/services/HelloService$ ./say_hello name="World"
         <section className="asterSection asterSection--paper">
           <div className="container">
             <FeatureBlock
-              kicker="AI-native"
+              kicker="MCP integration"
               title="Connect any AI agent to your services in one command."
               code={`# Expose your service to Claude or any MCP-compatible agent
 $ aster mcp <endpoint-addr>
@@ -557,17 +558,17 @@ $ aster mcp <endpoint-addr>
               </div>
 
               <div className="asterLaunchpad__actions">
-                <Link className="button button--primary button--lg" to="/docs/quickstart/python">
-                  Python quickstart
+                <Link className="button button--primary button--lg" to="/docs/quickstart/mission-control">
+                  Build Mission Control
                 </Link>
                 <Link className="button button--primary button--lg" to="/docs/quickstart/python">
-                  TypeScript quickstart
+                  60-second quickstart
                 </Link>
                 <Link className="button button--secondary button--lg" to="/docs/guides/define-a-service">
                   Define a service
                 </Link>
-                <Link className="button button--secondary button--lg" to="/docs/examples/hello-service">
-                  Hello service example
+                <Link className="button button--secondary button--lg" to="/docs/overview/aster-vs-grpc">
+                  Aster vs gRPC
                 </Link>
               </div>
             </div>