A portfolio-driven service architecture for design, code, research, and public automation.
PHI is the public interface for collections, portfolio, publishing, and request intake. PHI|OS is the manifest-driven superintelligence brain graph behind it, binding brain architecture, neural overlays, super-states, automation, and runtime surfaces across frontend, API, and storage.
Superintelligence brain graph for the PHI stack
PH|OS binds collections, users, requests, automation networks, domains, and LAB-linked brain architecture into one orchestrated graph surface. The public route exposes the overview, while the gated admin hub carries the live signal deck.
Live signal deck is gated
Homepage signal exposure has been removed. Live metrics, metadata signals, and request-state telemetry now resolve through the gated admin UI.
Primary SSR interface
Portfolio, CMS, service request intake, and public identity surface.
API boundary
Authentication, user management, CMS, project request, and public automation endpoints.
Media and storage boundary
Reserved for uploaded assets, portfolio media, and storage federation.
No published item yet
Publish the first collection element from the CMS to surface it here.
Current collections
The public homepage now reads directly from the live CMS collections stored in the database.
Current material from the collection
Research notes, source readings, and structured observations from the live CMS.
Content-driven service word cloud
Weighted service signals mined from published titles, excerpts, bodies, sections, tags, and categories across the live CMS.
Latest portfolio collections
The homepage portfolio surface now renders directly from the live CMS with image-driven masonry cards instead of the static photo block.
Join the conversation
Public groups, chat communities, and collaborative spaces.
Kobal Sigma LLM Integration
Social media automation powered by Kobal Sigma LLM from Akatsuki. Chat completion and content generation for cross-platform publishing.
Project intake stays public
The homepage no longer exposes recent requests or operational traces. Public visitors can still open the request studio, while request history and platform operations now live in the gated admin hub.
Connect and follow
Social profiles, communities, and public channels across networks.