REA-STYLE MINI-GRID CONCEPT
How SunShift would fit into a mini-grid.
The site sends readings. SunShift suggests one action. Safety rules check it. The existing site controller carries out an approved command.
01
THE 15 MINUTE LOOP
One clear path from reading to record.
-
1
Read the site
Sunlight, demand, battery level, generator state, temperature, and sensor health.
-
2
Check past days
Recall up to five dated records that match the site and load type.
-
3
Suggest an action
The agent can suggest START, HOLD, or STOP.
-
4
Apply safety rules
Battery reserve, minimum run time, sensor faults, and load risk are checked.
-
5
Send and record
The site controller receives an approved action. The full decision is saved.
TELEMETRYSUNSHIFT QAAPPROVED ACTION
Site PLC or energy management system
Owns the ATS, bypass switch, protection interlocks, watchdog, and manual control.
Public site references. This is not an REA deployment or endorsement.
02
PORTABLE AGENT MEMORY
What the agent remembers.
A memory record is a short dated note from an earlier simulated day. It records the site, load type, incident, and bounded context used by the policy. It is not a command.
BUILT ON MY EARLIER WORK
AgentQA is the portable memory behind this path.
I built AgentQA before SunShift QA, then plugged its remember and recall interface directly into this dispatch agent.
The default test stays offline. Portable storage is used only when AgentQA credentials are configured.- Encrypt
- AES-256-GCM protects each note with a key derived from the user's passphrase through scrypt.
- Store
- Walrus keeps the ciphertext in decentralized storage. The Sui blockchain provides the storage object and receipt.
- Recall
- Authorized agents use HTTP or MCP to recall the same project memory from another device.
CURRENT SEALED REPLAY
Checking memory match
Reading the generated evidence.
- Records matched
- Pending
- Reserve context
- Pending
- Confidence context
- Pending
DEVELOPMENT MEMORY ROUND TRIP
One record in. One new record saved.
This is generated from the real Kaduna development run. The sealed Abuja result above remains a zero-match case.
- RECALLPendingmatched before dispatch
- REMEMBERPendingReading receipt
- RECALL AGAINPendingmatched after the write
Checking whether memory changed this dispatch.
Memory examples did not load.The system layout is still available.
EXAMPLE TEST RECORDS
Choose a date
Loading record
Loading the first dated memory record.
- Reserve context
- Pending
- Forecast confidence
- Pending
- Incident
- Pending
- Record hash
- Pending
- Find a similar site and load day.
- Add a small, limited adjustment to the policy.
- Keep a dated research record.
- Start or stop the generator.
- Change battery or generator limits.
- Bypass the safety governor.
Each day becomes operating context.
The current build proves the record loop. Longer field history could support these engineering studies after calibration and review.
Compare similar cloud and demand periods before the agent proposes a start.
Needs site forecast validationReview the load, battery, and sensor sequence before recurring breaker or inverter events.
Needs synchronized device recordsCompare battery discharge or generator behaviour across days with similar operating conditions.
Needs long-term calibrated data
PORTABILITY RULE
Move the evidence. Keep authority site-specific.
A similar site can import reviewed records as research context. It does not inherit another site's equipment limits, protection settings, or permission to switch equipment.
FIELD RESEARCH PATH / REQUIRES SITE VALIDATION
03
AFTER EACH DAY
The outcome becomes evidence.
- 1
The system measures solar use, diesel use, battery movement, and missed load.
- 2
An engineer reviews faults, overrides, and the final result.
- 3
A short dated summary is stored with a hash.
- 4
A later run can recall it only when the site and load type match.