The 1view field guide
Understand what
you’ve built.
From your first specification to a difficult architecture question. Eight practical guides for finding your way through a product.
Start with the three-step workflowHow to use 1view: from a project to one connected canvas
Create an .ospec file with your own coding agent, open it locally in 1view, and explore architecture, features, data and requirements.
02ArchitectureRead a technical architecture beyond boxes and arrows
Explore services, hosting boundaries, APIs, queues and external dependencies in 1view, and distinguish product responsibilities from deployment topology.
03FeaturesUnderstand one feature across your entire stack
Use 1view feature views to follow a capability through UI, APIs, services, data, flows and requirements without creating a separate specification.
04DataExplore a large database schema one relationship at a time
Read exact column-to-column relationships, database technology labels and focused table neighborhoods in 1view without losing the complete schema.
05BehaviorTrace API calls, queues and failure paths in one product view
Use behavior and interaction diagrams in 1view to follow synchronous calls, asynchronous events, retries and durable state changes.
06AuthoringAsk a coding agent to document your project systematically
Use 1view’s staged agent instructions to investigate source files, components, relationships, data and behavior, then produce one validated .ospec file.
07UnderstandingStay oriented when agents build faster than you can review
Use a connected product specification to review agent-built software, trace ownership and dependencies, and separate requirements from verified behavior.
08Files & handoffsKeep your product specification portable and under your control
Understand what an .ospec contains, how 1view processes it locally, and how to export, preserve and share a complete product specification.
