Static wiki for the IEEE Smart Village working group. No Node install for browsing — HTML + one tiny local HTTP server.
AI assistants: read AGENTS.md first. Discovery: llms.txt, auth.md, .well-known/ai-catalog.json. Cloudflare dashboard steps (Markdown for Agents, headers): technical-notes/AGENT-READINESS-CLOUDFLARE.md.
Need network once to clone. After that, wiki + Village Simulator work without internet (basemap tiles / live GitHub Issues / Mapbox map may be empty offline — core pages and the sim still load).
git clone https://github.com/overview-solutions/isv-ai-wiki.git
cd isv-ai-wiki
./preview.shThen open:
| What | URL |
|---|---|
| Wiki home | http://127.0.0.1:8765/index.html |
| Village Simulator (inside wiki) | http://127.0.0.1:8765/index.html#village-metering/village-simulator — how to open live app + run locally |
| Nairobi workshop / code challenges | http://127.0.0.1:8765/power-africa-2026-workshop-planning.html |
| OMS Workshop Nairobi | http://127.0.0.1:8765/oms-workshop-nairobi-2026.html |
Live simulator (no install): overview-solutions.github.io/smart-village-simulator. Source: smart-village-simulator. Wiki hub: #village-metering/village-simulator. If the in-page frame is blank, use the live URL in a new tab. v1 freeze village-simulator/ is an old snapshot only — do not develop there.
Do not double-click index.html in Finder/Explorer — file:// breaks fetch, Tasks, and the sim iframe. Always use ./preview.sh (needs Python 3, already on macOS/most Linux).
Only if you are changing sim code (not just reading the wiki):
# sibling folder next to this clone, e.g. ../smart-village-simulator
git clone https://github.com/overview-solutions/smart-village-simulator.git
cd smart-village-simulator
npm install && npm start # http://127.0.0.1:5176See that repo’s README for Locus / offline map packs. Do not edit the wiki’s frozen village-simulator/ for product work.
Live site: isv.wiki · GitHub Pages mirror
Live Village Simulator: overview-solutions.github.io/smart-village-simulator
Source: github.com/overview-solutions/isv-ai-wiki (MIT)
This wiki is open — anyone can read it. A small amount of material (vendor contacts and outreach status, real pricing, NDA-gated docs, unconsented personal details) is kept in a separate access-controlled repo, isv-ai-wiki-private. We publish the rules so you can see exactly what we protect and why:
SHARING-POLICY.md— what's public, what's private, and how to request access (this doc is itself public, on purpose).- Contributors & AI assistants: the boundary is one-directional — private may inform public in the abstract, but no private fact, name, price, or NDA quote is ever copied into a public file. See
AGENTS.md→ Public / private split. - Editing both at once? Open
isv-wiki.code-workspacein Cursor/VS Code for a multi-root view of both repos as shared context.
| Section | What it is |
|---|---|
| Tasks | Meeting follow-ups as GitHub Issues — live board in the wiki |
| Meeting notes | Internal Tech Comm call notes (tables, action items, embedded diagrams) |
| Events & Workshops | In-person results and upcoming (Power Africa OpenAMI EMS workshop · OMS Nairobi · OSEAS) |
| Village Metering | Benchmarks, roadmap, MeshEMS board, VMRS/OBIS registers, vendor study, Village Simulator |
| Technical reports | Dev Labs + ISV reports (catalog.json) — summaries here, full docs linked |
| Standards | Village-relevant (2030.10, DLMS, STS, SunSpec) vs larger grid integration (1547, 2030.5, 2800, P4200) |
| Everything else | About ISV, supported projects map, resources |
Direct links (live site):
- Tasks board (wiki) — filter by meeting, status, assignee
- GitHub Issues (source of truth) — create, comment, assign, close
- Power Africa 2026 Workshop — results: 4 sessions ran (3 Mon + 1 Thu); BUILD sim · Open Utility Network convention
- OMS Workshop Nairobi — 30 Sep–2 Oct 2026 · A2EI · EnAccess
- Metering topology meeting note
- Meter vendor study — cited benchmarks, STS, DLMS, industry bands
- Standards guide — village microgrid standards vs larger grid integration
- Circles of Power · ISV-HCK-001
- Technical reports
- Dev Labs report library (full documents)
- Source repo — openami-smart-village (reports on GitHub)
- Copy
tech-comm-2026-05-28-metering-topology.htmlas a template. - Register the note in
index.html→MEETING_NOTES(sidebar + iframe preview). - Push to
main— GitHub Pages updates in ~1 min.
Reports are indexed in the wiki, hosted on Cottonspace, and maintained in GitHub:
- Browse summaries in the wiki → Technical reports sidebar
- Open the full document via Open full report ↗
- Live library: sattal.cottonspace.com/reports
- Source repo: github.com/rahulbhargavain/openami-smart-village
Reports use IDs like EMG-TRD-005 = Emerging markets · Technical reference · #005. See the collapsible key on the Technical reports page.
Listing (automatic): Opening Technical reports in the wiki fetches the live openami-smart-village reports index from GitHub (same source Cottonspace publishes). New reports appear without running a sync script or redeploying.
Enrichments (manual): technical-notes/catalog.json holds wiki-only entries (e.g. ISV-HCK-001, external industry PDFs) and optional ISV context (isvRelevance, relatedMeetingNotes, provenance tags, tags) merged by report ID. Edit that file when you want richer summaries on specific reports.
Provenance (optional per item): sourceKind (dev-labs | isv-wiki | external), authorship (human-primary | ai-assisted | mixed), reviewStatus (committee-reviewed | draft | index-only). Omitted fields use defaults documented in reportProvenanceGuide.
Optional — refresh enrichment stubs after bulk Cottonspace changes:
cd isv-ai-wiki
python3 technical-notes/sync-catalog.pyWiki-only entries have "syncProtected": true and are always preserved.
To add ISV-specific context manually, edit fields in technical-notes/catalog.json:
{
"id": "short-slug",
"reportCode": "EMG-XXX-000",
"title": "…",
"publisher": "Cottonspace Dev Labs",
"published": "May 2026",
"type": "technical-reference",
"category": "Technical Reference",
"tags": ["OpenAMI", "metering"],
"url": "https://sattal.cottonspace.com/reports/your-report.html",
"sourceFile": "reports/your-report.html",
"githubUrl": "https://github.com/rahulbhargavain/openami-smart-village/blob/main/reports/your-report.html",
"sourceCatalog": "cottonspace-dev-labs",
"summary": "What it is.",
"isvRelevance": "Why ISV cares.",
"relatedMeetingNotes": ["metering-2026-05-28"]
}Integration options (current vs future):
| Approach | What it does |
|---|---|
| Catalog index (now) | Wiki lists metadata; links out to Cottonspace for the full report |
| Catalog sync script (now) | technical-notes/sync-catalog.py pulls from openami-smart-village GitHub |
| Self-hosted copy (future) | Mirror report HTML into this repo for offline / archival |
| Iframe embed (future) | Show report inline in the detail panel (needs Cottonspace embed consent) |
Refresh the wiki after editing the catalog. Old #tech-notes/… links still work; new links use #tech-reports/….
The metering topology map is technical-notes/diagrams/metering-topology.svg.
On the meeting note page, above the diagram:
- Download SVG
- Import into diagrams.net → File → Import From → Device
- Export SVG, replace the file in the repo, refresh
Text-only tweaks: edit the .svg in Cursor (see technical-notes/diagrams/EDITING.md).
Action items from meetings are not stored in tasks.json anymore. They are GitHub Issues on this repo (overview-solutions/isv-ai-wiki).
| View | URL | Best for |
|---|---|---|
| Wiki task board | index.html#tasks | Summary stats, filters by meeting/status/assignee, links into each issue |
| Meeting note panel | Top of each meeting note page (e.g. #notes/metering-2026-05-28) | Follow-ups for that session only |
| GitHub Issues | github.com/…/isv-ai-wiki/issues | Full history — comments, assignees, labels, close/reopen |
| GitHub Projects (optional) | Repo → Projects tab | Kanban across issues if you add a project board |
The wiki reads issues from the public GitHub API on page load. Create and update on GitHub — comment for updates, close when done. The wiki reflects changes the next time you open or refresh the Tasks page.
- New issue → Follow-up task template
- Describe the work, assignee, and context
- Add a meeting label on the issue sidebar, e.g.
meeting-metering-2026-05-28ormeeting-power-africa-2026-workshop-planning - Optional:
in-progress,blocked,priority-high, etc.
Label setup (one-time, for maintainers): see tasks/README.md.
GitHub only has open vs closed. The wiki maps that plus labels and comments:
| On GitHub | Wiki shows |
|---|---|
| Issue closed | Done |
Open + blocked label |
Blocked |
Open + in-progress label |
In progress |
| Open + at least one comment | In progress |
| Open, no comments, no status labels | Not started |
Comment on an issue when work starts — no extra label required. Add blocked or in-progress labels if you want to override that logic.
Meeting metadata and label names live in tasks/config.json. Legacy pre-Issues catalog: tasks/tasks-archive.json.
isv-ai-wiki/
├── tasks/
│ ├── config.json # GitHub repo + meeting labels for Issues UI
│ ├── tasks-archive.json # Legacy catalog (pre-Issues migration)
│ └── README.md # Labels setup + workflow
├── tasks.html # Redirects to index.html#tasks
├── css/isv-tasks.css # Follow-up panels + task table styles
├── js/isv-tasks.js # Loads GitHub Issues API + config
├── js/isv-theme.js # Theme toggle (default light, localStorage)
├── index.html # Wiki shell + navigation
├── preview.sh # Local server (port 8765)
├── tech-comm-*-*.html # Meeting note pages
├── stonehenge-microgrid-topology.html # Open Energy Hackathon concept (Apr 2025)
├── technical-notes/
│ ├── catalog.json # Technical reports index
│ ├── sync-catalog.py # Sync from openami-smart-village GitHub
│ └── diagrams/ # SVG diagrams for meeting notes
├── js/ # Funded projects map embed
└── .github/workflows/deploy.yml # Deploy to GitHub Pages on push
This wiki is fully open source and hosted for free on GitHub Pages.
| Repository | github.com/overview-solutions/isv-ai-wiki |
| Live site | overview-solutions.github.io/isv-ai-wiki |
| License | MIT (LICENSE) |
| Tasks / follow-ups | GitHub Issues on the same repo |
| Deploy | Push to main → GitHub Actions (.github/workflows/deploy.yml) publishes static files |
There is no server to maintain for the wiki itself: content is HTML, CSS, and JSON in git. GitHub builds and serves the site with HTTPS. Supported Projects shows a static map screenshot that links to the live RemoteMonitorMap. Mapbox token (optional) is only needed if you still deploy map-embed.html.
Contribute content: fork or branch → edit files → open a pull request. Meeting notes, catalog entries, and task labels/issues all live in this repository.
Write access (collaborator): Anyone can fork and open PRs without being added to the repo. To be added as a GitHub collaborator (push directly, manage issues with full repo access), email Adam Sauer, Tech Comm Committee Chair, at adam.r.sauer@ieee.org.
Contribute code: same flow. Local offline kit: ./preview.sh (see top of this README). Do not open index.html via file://.
First-time Pages setup (maintainers): repo Settings → Pages → Source: GitHub Actions.
Push to main. The workflow publishes to GitHub Pages automatically (~1 minute).
Site URL: https://overview-solutions.github.io/isv-ai-wiki
AI editing — sidebar status dot → paste an Anthropic API key → Edit with AI on any section. Key stays in your browser only.
Mapbox — optional. Supported Projects no longer iframes the live map. MAPBOX_PUBLIC_TOKEN is only needed if you still deploy map-embed.html (see deploy.yml). Without it, that standalone page shows a setup message.
Pull requests welcome for wiki content (meeting notes, catalog entries, etc.).
Meeting follow-ups go through GitHub Issues, not PRs to a task file:
- Open a new follow-up
- View all issues
- Wiki task board for a filtered summary
You need a GitHub account. Anyone can comment on public issues; to push to the repo or be assigned as a collaborator, email Tech Comm Chair Adam Sauer at adam.r.sauer@ieee.org. Sign up as an ISV volunteer at smartvillage.ieee.org/volunteer if you are not on the team yet.
MIT · IEEE Smart Village · Overview Solutions LLC