AI Initiative logoAI Initiative
Reading room / Manthan

Per-node Charter / LOTS / privacy-policy

Per-node Charter / LOTS / privacy-policy. Covers What's filled in (D-003); Pre-deploy Charter customisation; from the repo root, after deciding on a real deployment domain:; also update the tfvars so the ALB / Route 53 / ACM align:.

Project explanation / technical method
This is the retained source text, not a new validation of its claims. Numerical results and comparative claims require the accompanying source review before public reuse.

Read the connected case study or article →

Not explicitly stated in source · Date not established

Provenance, authorship and editorial notes

Per-node Charter / LOTS / privacy-policy

Id

manthan-herald-protocol-services-testnet-nodes-readme

Project

Manthan

Source path

manthan/herald-protocol/services/testnet/nodes/README.md

Source sha256

0eeb8a94e4c1180fcd15b9ae0a86e0a09d1cf16cd9216c109657ffa46fadbc96

Local copy sha256

0eeb8a94e4c1180fcd15b9ae0a86e0a09d1cf16cd9216c109657ffa46fadbc96

Repo head

3a94084024a3434cef331fecac91c2c3b43f0313

Date
Not recorded
Date basis

Original publication date not established; Git revision date retained separately.

Author

Not explicitly stated in source

Author basis

Unknown; Git committer not substituted for document author.

Last source commit

8b75d1b0157c20a0a463f0e31008ef9f73099beb

Last source commit date

2026-06-08T07:40:14Z

Document status

Project explanation / technical method

Summary

Per-node Charter / LOTS / privacy-policy. Covers What's filled in (D-003); Pre-deploy Charter customisation; from the repo root, after deciding on a real deployment domain:; also update the tfvars so the ALB / Route 53 / ACM align:.

Topics
  • Exploration architecture and selection
  • What's filled in (D-003)
  • Pre-deploy Charter customisation
  • from the repo root, after deciding on a real deployment domain:
Theme

Exploration architecture and selection

Priority

deep

Related ids
  • manthan-readme
  • manthan-docs-architecture
  • manthan-docs-business-overview
  • manthan-docs-demo-walkthrough
  • manthan-docs-principles
  • manthan-docs-qd-measurement-direction-plan
  • manthan-docs-swarm-evolution-integration
Evidence concerns
  • Recovered source text is preserved verbatim. Assertions, comparisons, commands and results belong to its original context; they were not re-executed or externally re-verified during this corpus review.
Word count

392

Bytes

2793

Source relative

herald-protocol/services/testnet/nodes/README.md

Remote mirror

manthan/herald-protocol/services/testnet/nodes/README.md

Full text preserved

True

Per-node Charter / LOTS / privacy-policy

This directory holds the live Charter, LOTS, and privacy-policy markdown for
each genesis node. Each set is signed at startup by the running node:

What's filled in (D-003)

The Charters and LOTS are filled in for a v0.2 single-operator UK testnet. Concrete values:

FieldValue
OperatorKulbir Minhas, individual researcher (sole-operator; not incorporated)
CountryUnited Kingdom
Jurisdiction for service of processEngland and Wales
AWS regioneu-west-2 (London)
Compulsion exposureInvestigatory Powers Act 2016, UK GDPR / DPA 2018, PACE 1984, UK-US DAA 2019 (CLOUD Act partner)
Warrant canarymonthly, signed under herald.canary.v1, served at /canary
Cross-signingeach node lists the other two by name in §7.1

These satisfy the D-003 acceptance criteria in PHASE_5_HANDOFF.md §4.

Pre-deploy Charter customisation

Before a live AWS apply, the operator MUST search-and-replace the deployment
domain in all 9 files. The default value (testnet.manthan.example.com) is
RFC-2606 reserved-for-example and won't resolve.

# from the repo root, after deciding on a real deployment domain:
DOMAIN="testnet.manthan.acmeresearch.io"      # change this

find herald-protocol/services/testnet/nodes -name '*.md' -print0 \
  | xargs -0 sed -i "s/testnet\.manthan\.example\.com/${DOMAIN}/g"

# also update the tfvars so the ALB / Route 53 / ACM align:
sed -i "s/testnet\.manthan\.example\.com/${DOMAIN}/g" infra/terraform/envs/testnet.tfvars

If the operator legal entity, country, or jurisdiction differs from this
template, edit Charter §1 / §5, LOTS §1 / §7, and privacy-policy §0 / §6
before re-signing.

S3 archival (D-003 final acceptance bullet)

After the AWS stack is applied (D-002), upload the signed Charters / LOTS /
privacy-policies to the versioned S3 bucket:

./infra/scripts/upload-charter-to-s3.sh

The script reads the bucket name from the Terraform output and uploads each
file under s3://<bucket>/nodes/<name>/{charter,lots,privacy-policy}.md.
Versioning is enabled on the bucket so older revisions are retained
indefinitely; supersession (Charter §10, LOTS §11) is just "upload a newer
version".

Re-signing on update

Charter / LOTS edits don't require redeploy: edit the markdown, restart the
ECS service (aws ecs update-service --force-new-deployment), and the new
file is signed at task startup. The old version stays in the S3 archive.

Continue exploring