Clarify Solana deployment model and typecheck flow

Author: X-PACT

BUILD.md

@@ -117,6 +117,28 @@ This repository already has a deployed devnet program and published references t
 
 If you intentionally deploy a fresh program for your own environment, treat that as an environment-specific override, not as a silent documentation update.
 
+## What Deployment Means Here
+
+"Deploying to Solana" in this repository means deploying the Anchor program binary to a Solana cluster such as devnet.
+
+It does not mean:
+
+- uploading the whole GitHub repository on-chain
+- storing the docs frontend on-chain
+- moving your scripts, SDK, or markdown files into Solana accounts
+
+What stays off-chain:
+
+- the repository and source history
+- the docs/frontend hosting
+- the CLI scripts and migration helpers
+- operator workflows and CI
+
+What goes on-chain:
+
+- the compiled program
+- the accounts created and managed by the program during DAO operation
+
 ## Helpful checks
 
 ```bash

README.md

@@ -54,6 +54,20 @@ That context matters for positioning, but this repo does not claim prize results
 - Local tests cover commit, reveal, finalize, execute, cancellation, delegation, keeper reveal, and treasury validation paths
 - This repo is production-minded, but still devnet-first and not represented as a completed mainnet governance system
 
+## What Goes On Solana
+
+For this kind of project, you do not upload the whole repository to Solana.
+
+- The on-chain program is what gets deployed to the Solana network
+- The repository stays in GitHub as the source of truth for code, scripts, SDK, docs, and frontend assets
+- The docs frontend can be hosted separately, such as GitHub Pages
+- Operators and users interact with the deployed program through RPC, wallets, scripts, SDK calls, or the frontend
+
+So if the question is "does the project need to be on Solana?", the practical answer is:
+
+- yes, the program should be deployed on Solana if you want a real working product
+- no, the rest of the project is not stored on-chain and should not be treated as something you "upload to Solana"
+
 ## What Exists Today
 
 - Commit-reveal voting with hidden tally during the voting window

scripts/verify.sh

@@ -43,6 +43,16 @@ verify_test() {
   "$ANCHOR_BIN" test --skip-build --skip-deploy
 }
 
+verify_typecheck() {
+  echo "[verify] typescript typecheck"
+  if [[ -x "./node_modules/.bin/tsc" ]]; then
+    ./node_modules/.bin/tsc --noEmit
+  else
+    echo "[verify] missing local TypeScript compiler. Run npm install or yarn install first." >&2
+    return 1
+  fi
+}
+
 verify_scan() {
   echo "[verify] non-real-code scan"
   local pattern
@@ -96,6 +106,9 @@ case "$mode" in
   scan)
     verify_scan
     ;;
+  typecheck)
+    verify_typecheck
+    ;;
   rpc)
     verify_rpc
     verify_rpc_health_unit
@@ -109,6 +122,7 @@ case "$mode" in
   all)
     ensure_required_tools "NODE_BIN:node" "ANCHOR_BIN:anchor" "SOLANA_BIN:solana" "CARGO_BIN:cargo"
     verify_tools
+    verify_typecheck
     verify_fmt
     verify_lint
     verify_build
@@ -119,7 +133,7 @@ case "$mode" in
     verify_rpc_health
     ;;
   *)
-    echo "Usage: $0 [all|tools|fmt|lint|build|test|scan|rpc|rpc-health|rpc-health-unit]" >&2
+    echo "Usage: $0 [all|tools|typecheck|fmt|lint|build|test|scan|rpc|rpc-health|rpc-health-unit]" >&2
     exit 2
     ;;
 esac