GeoSync

Verification-first quantitative research infrastructure for falsifiable market-structure hypotheses.

GeoSync is not a trading bot.
GeoSync is not an alpha product.
GeoSync is not a proof that markets obey any asserted physical law.

It is a research platform where claims are permitted only when they are bound to explicit invariants, data contracts, falsifiers, reproducible artifacts, and release evidence.

---

∴ Research Kernel

Most market-research repositories optimize for narrative confidence.

GeoSync optimizes for something less fashionable and more useful:

A claim may exist only when it can identify its invariant, data source, method, artifact, falsifier, and replay path.

No replay.
No falsifier.
No evidence.
No claim.

---

System Spine

DOCTRINE / FORBIDDEN CLAIMS
        ↓
CLAIM REGISTRY
        ↓
112 MACHINE-CHECKABLE INVARIANTS
        ↓
DATA CONTRACT
        ↓
SEMANTIC CONTROL LAYER
        ↓
INFERENCE READINESS CONTRACT
        ↓
INFERENCE OPERATION PROTOCOL
        ↓
NULL BASELINES / FALSIFIERS
        ↓
ARTIFACT VALIDATION
        ↓
RELEASE EVIDENCE HARNESS
        ↓
EXTERNAL REPRODUCTION

GeoSync treats research as engineered infrastructure, not as a decorative chart factory wearing a lab coat.

---

Repository Map

Surface	Purpose
PRODUCT_CATEGORY.md	Canonical product-category boundary.
CLAIMS.md	Claim tier ledger and evidence pointers.
FORBIDDEN_CLAIMS.md	Status-language firewall and promotion invariants.
docs/REPOSITORY_SYSTEM.md	Operational map for reviewers, auditors, and implementation agents.
docs/SEMANTIC_CONTROL_LAYER.md	Role-bound semantic control layer that turns repository files into filter, context, claim, boundary, test, verdict, schema, evidence, and replay surfaces.
docs/INFERENCE_READINESS.md	Runtime-readiness contract for context, agent, artifact, and falsification control.
docs/INFERENCE_OPERATION_PROTOCOL.md	Seven-step agent runbook for converting repository meaning into bounded execution.
docs/INFERENCE_CONTRACT.manifest.json	Machine-readable manifest for authority files, reading order, gates, stop conditions, and required agent state.
AGENTS.md	Implementation-agent contract: prime directive, canonical files, required/forbidden behavior, and the evidence-bearing artifact minimum.
docs/governance/AUTONOMOUS_AGENT_EXECUTION_PROTOCOL.md	Autonomous-agent execution contract: delegated authority, owner-only merge, frozen-artifact protection, and the mandatory perturbation matrix beyond green tests.

Research boundary

GeoSync is HYPOTHESIS/INSTRUMENTED-first: a green terminal line is NOT EVIDENCE-BEARING until an artifact carries it. Synthetic data may exercise a mechanism and bound its failure modes, but it never promotes a claim about real markets. Schema validity proves shape, not truth. Promotion happens only through the CLAIMS.md tier ledger under the gates in docs/REPOSITORY_SYSTEM.md.