Public release
Android shipped with a full gate
Build, hash, download-back, physical install, VPN and shalCord smoke.
Flagship case · shalPIN product system
One product.
Every hard layer.
Full-stack product engineering from a tap on Android to the service that proves it. shalPIN brings together private networking, realtime communication, identity, money, backend services, and disciplined delivery.
Report-backed claims
Real-device verification
Honest delivery status
Multi-generation lab
Fold 2→7, phones, tablet, laptop
Six Fold generations, S23 Ultra, four A-series phones and larger screens.
Live services
Go and PHP working together
Account gateway, sessions, access policy, billing and delivery health.
2-device proof
Visible remote video
Incoming call, accept, shared room, remote video on both devices, clean end.
Owner device evidence archive
Built against a device matrix, not a lucky handset.
SHAL proof spans six Galaxy Fold generations, flagship and A-series phones, Android tablets, and Windows laptops. Current release gates stay deliberately narrow; the wider archive preserves compatibility history across the product.
Install + launch
UI + navigation
VPN + routes
Realtime pairing
Windows runtime
Current canonical gate
Owner evidence archive
Galaxy Z Fold generations
Fold 2 through Fold 7
02
03
04
05
06
07
Galaxy phones
Flagship + A series
S23 Ultra
A11
A51
A52
A55
Larger surfaces
Android + Windows
Android tablets
Windows lab laptop
Evidence depth differs by ticket: this matrix does not imply that every feature passed on every device. Current canonical product gates name S23 Ultra, Fold4, Fold7 and one Windows lab laptop; older owner-device evidence remains in the archive.
01 · The system
A product is the path between layers.
SHAL work crosses the seams where product failures usually hide: UI and runtime, runtime and backend, backend and operations. Each status below reflects its actual proof level.
Product surfaces
shalPIN for Android
Product shell, identity, contacts, conversations, privacy and notifications.
Windows client
Direct Go session path verified; clean-environment full egress remains in progress.
Runtime layers
shalVPN lifecycle
Route snapshot, protected session, heartbeat, release and visible Power state.
shalCord + rooms
Messages, linked notifications, call flow and real two-device remote video.
Service truth
Go control plane
Sessions, route state, idempotent ledger, scheduled billing and service health.
PHP account gateway
Identity, compatibility, registration and product access without split money truth.
Public or live service
Owner-lab accepted
In progress
Case 01 · Android + private network
Public release
Physical device proof
Make the Power button mean a real network state.
A connected label is not a VPN. The product state had to agree with Android runtime, the protected route, the server lease, and the eventual release.
- Connected the visible control to service lifecycle and route truth.
- Preserved billing, session limits, heartbeat and release behavior.
- Closed the release with download-back and physical install proof.
Physical VPN Power smoke
Clean baselineBase internet available, tunnel absent
Pass
Visible startUser action enters Android service lifecycle
Pass
Protected routeTunnel present, expected egress and lease
Pass
Clean stopTunnel absent, lease released, base internet intact
Pass
Release integritySHA, download-back, install and app smoke
Pass
Case 02 · shalCord + video
Owner-lab accepted
Two-device proof
Turn realtime features into one coherent product layer.
Messaging, contacts, notifications and calls cannot behave like separate demos. shalPIN now carries linked product state from the conversation to Android notifications and into a real two-device video flow.
- Built profile, privacy, contacts, requests and conversation-state surfaces.
- Linked unread state, grouped notifications, deep links and swipe dismissal.
- Proved incoming video, accept, shared room, remote render and clean end on two devices.
Verified remote render path
Visible both ways
Case 03 · Money + access truth
Owner-lab live service
Idempotent ledger
Put billing and access behind one source of truth.
A PHP account surface and a Go control plane once had overlapping responsibilities. The accepted design keeps compatibility at the gateway while money and active-session truth remain authoritative and repeatable.
- Built an idempotent ledger bridge that does not double-credit on retry.
- Added scheduled daily debit with duplicate suppression and service health checks.
- Kept backup, rollback and post-deploy smoke in the same delivery ledger.
One truth · repeat-safe transitions
event 01
PHP gateway eventAuthenticated compatibility boundary
Accepted
event 02
Go ledger transitionSingle authoritative money write
Applied
retry 01
Duplicate deliverySame key, no second balance mutation
No-op
schedule
Daily access cycleHealth-checked and rollback-ready
Healthy
02 · Owned layers
Capabilities tied to shipped work.
Not a keyword wall. Each capability below maps to an accepted product layer, a live service, or a bounded owner-lab proof.
Android product delivery
Product shell, stateful UX, service lifecycle, notifications, privacy, packaging and physical-device closure.
Private network runtime
Session admission, route snapshots, protected egress, heartbeat, limits, release and truthful Power state.
Realtime product systems
Messages, contacts, requests, notification routing, room admission and two-device visible video.
Go control services
Authoritative session and money state, idempotent transitions, scheduled work, health and readiness.
PHP product gateway
Account and registration compatibility, authenticated bridging and clean boundaries around service truth.
Release operations
Layer preservation, build identity, private scan, backup, rollback, download-back, install and smoke.
03 · Verification register
Delivery status without theatre.
Public, owner-lab, live service, in progress, and R&D are different claims. This portfolio keeps those boundaries visible.
2026 · Android
Public release
Release-gated shalPIN Android build
Hash · install · VPN · app smoke
2026 · Product
Owner-lab accepted
Profile, privacy, conversations and linked notifications
Physical UI and state proof
2026 · Video
Two-device proof
Incoming, accept, shared room, remote video, clean end
Visible render on both devices
2026 · Backend
Live service
Idempotent ledger and scheduled daily access cycle
Health · retry · rollback
Next · Clients
In progress
Windows full-egress proof and persistent group rooms
Boundaries explicitly open
Lab · AI
R&D only
Controlled state routing and anti-leak regression research
Source and dataset checks
Claim boundary
Persistent group-room completion, call audio, and Windows clean-environment full egress
are not presented as delivered. Private scans are delivery gates, not independent security audits.
04 · How the work closes
Evidence is part of the implementation.
The goal is not source that looks complete. It is a bounded change that preserves accepted layers and survives the real path.
Recover product truth
Start from accepted heads and current behavior, not whichever branch happens to be open.
Preserve layers
List the working contracts that the change is not allowed to regress.
Change narrowly
Keep the patch legible and the product decision inside the agreed scope.
Prove the path
Exercise the device, service, state transition, or delivery route that users actually touch.
Close reversibly
Record build identity, health, backup, rollback and the exact remaining boundary.
Bring the difficult slice
Need someone who can cross the product boundary?
Share the failing path, the intended outcome, and the access boundary. I can scope a milestone across UI, runtime, backend, and delivery—without pretending unfinished work is done.
a.shalafan@gmail.com
Scoped projects · milestone delivery