iisacc logo

Contents

A curated working archive for technical documents, solution stories, technical decisions, and studio material from iisacc.

Abstract geometry archive hub with blue glass modules
Cover of Software Engineering for Shipping Vibe-Coded Products
01 / Free English eBook

Software Engineering for Shipping Vibe-Coded Products.

A 77-page field guide to turning AI-proposed changes into software that survives architecture review, tests, packaging, deployment, payment, delivery, and operations.

  • Complete first edition
  • PDF and EPUB
  • English only
  • No checkout

Free to read and download for personal learning and the reader's internal work. Copyright is retained; resale and redistribution are not permitted. Read the free-edition notice.

Geometry technical archive made of layered dark planes
02 / Technical archive

LVRS documentation, shaped for fast reading.

Route-ready framework docs are organized as a navigable studio reference instead of a flat file dump.

Geometry canvas workflow with brush arcs and construction planes
03 / solution workflow

Sketch, annotate, and export ideas through Vincent.

A canvas-first tool connects the technical and solution material in this archive.

Geometry studio origin timeline made of floating slabs
04 / Studio story

The origin notes behind the Vincent build.

Development context, design judgment, and the practical reason the tool exists.

Geometry world map made of dark nodes and blue routes
05 / World

Future releases and wider studio updates.

A place for new directions, collaborations, and solution-line changes.

Technical judgment notes

The archive records why the tools are shaped this way.

These notes stay inside Contents because they are reference material, not a separate brand section. They explain the pressure behind the technical choices so solution pages can stay focused on what shipped.

Qt / QML

Desktop behavior comes before web-like convenience.

Vincent needs real windows, local files, pointer input, keyboard shortcuts, and a UI layer close to C++ painting code.

Cross-platform desktop

A clear release surface keeps the solution honest.

Vincent is presented as a cross-platform desktop app so packaging, installation, and daily testing can be described without implying a single-platform direction.

Raster core

The feel of a mark is part of the solution contract.

Brush softness, layer behavior, undo boundaries, and export quality need solution-owned rendering work instead of a generic document model.

Local first

The cloud should be optional, not the owner of the work.

Screenshots, sketches, rough notes, and private drafts should begin on the user's machine and leave only when the user chooses.