Open
Conversation
Adds RESTRUCTURE.md (rationale, audience analysis, migration plan) and mint.proposed.json (new Mintlify navigation config). Key changes: lead with verifiable computation not blockchain, add trust model section, add agent integration as peer path, relocate Ethereum-specific concepts into guides. Terminology aligned with concept-map.md from docs-plan repo.
Replaces mint.json with proposed navigation structure: - Getting Started, Core Concepts, Guides, Use Cases sections - API Reference split into Compute, Verify, Records groups - New Trust Model section - Resources section with research and changelog
- Introduction: lead with verifiable spatial computation, not Ethereum - Quickstart: curl-first approach, 4 clear steps, onchain is optional - How-it-works: rename Policy Engine to Compute Engine, update diagrams Reframes the entry point for a wider audience beyond blockchain developers. Blockchain integration is positioned as one path among several (agents, backends, compliance).
New pages: - geocomputation.mdx (from geospatial-operations, terminology updated) - geographic-features.mdx (from location-attestations, provenance section) - result-format.mdx (from policy-attestations, universal framing) - privacy-model.mdx (new: TEE privacy guarantees and limitations) Edited: - verifiable-computation.mdx (trust model content extracted) - location-proofs.mdx (terminology: geocomputation, signed result) Original files preserved for reference.
New guides: - local-development: Docker, env setup, --env-file startup - calling-the-api: request/response format, input types, errors - blockchain-integration: EAS resolvers, delegated attestations - agent-integration: Python/TS examples, decision-making patterns - building-plugins: PoL plugin interface, Wi-Fi example - verifying-location-proofs: claims, stamps, credibility scores blockchain-integration merges content from eas-resolvers, policy-attestations onchain sections, and location-attestations storage options.
- delivery-verification: escrow + proximity resolver - parametric-insurance: crop insurance with distance threshold - geofence-compliance: drone corridor monitoring - onchain-attestation: NFT minting, token distribution patterns Each page uses story framing with concrete code examples. delivery-verification relocated from guides/ with terminology updates.
Extracted from verifiable-computation.mdx and security.mdx: - architecture: TEE execution model, container design, stateless model - what-is-verified: signature coverage, input references, reproducibility - what-you-are-trusting: honest trust assumptions, GPS spoofing caveat - security: signer address, replay attacks, best practices, key rotation Separates "how it works" from "what you should trust" for clearer reasoning about the system's guarantees.
- api-reference/compute/*: relocate 6 operation pages to subdirectory - api-reference/verify/*: split verify.mdx into stamp, proof, plugins - sdk/types.mdx: TypeScript type definitions reference - resources/research.mdx: links to location proofs paper, research agenda - resources/changelog.mdx: v0.1.0 research preview entry
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restructures docs from blockchain-first framing ("geospatial policy engine for Ethereum") to wider "verifiable spatial computation" framing. Blockchain is one integration path alongside agents, APIs, and compliance systems.
Known remaining work
Test plan