Code record
All 60 source files were recorded with SHA-256 checks.
Don’t take our word for it. Check the build.
Follow one real Entea app from the first brief to its code, checks, AWS launch, rollback, and recovery. Every number comes from the saved build record.
The AWS app was online when checked on 18 September 2026 at 12:47 UTC.
The brief came first.
The published record is the original request. Only the personal email address and phone number were removed.
“Update the existing Ankit Portfolio Studio application with the verified portfolio content from the attached resume. This is an application update, not a request to merely return JSON.”
It asked for real code and safe database updates, with public pages, private editing, drafts, publishing, search visibility, stable content order, and no invented facts.
Original brief
Read the original brief SHA-256 27b2e76f…6596f3cSee how the pieces fit.
This is more than a clickable mockup. It has public pages, a private owner area, working data connections, and its own database space.
- 1
The brief
A saved brief defines the public portfolio, private editing area, content flow, security, database, and success checks.
- 2
The build trail
The plan, code generation, database approval, checks, and preview are recorded for the same app.
- 3
The app
A Next.js and React application with TypeScript, secure data access, APIs, and a private owner workspace.
- 4
Its own database space
App-specific PostgreSQL tables and a safe update keep this app’s data separate.
- 5
The live release
A locked release image runs on AWS over HTTPS, with launch, domain, rollback, and cleanup events saved.
Who can do what
Visitor
Views the published portfolio, resume, and projects, and can send a checked contact form.
App owner
Signs in to edit content, manage drafts, publish updates, read messages, and manage files.
Entea
Builds and checks the code, but cannot give itself owner access.
Release manager
Approves database changes and launches a checked version in the connected cloud.
How the data is organized
Seventeen app-only tables store identity, content, publishing, messages, files, and usage events. Related records stay connected.
Identity
users · profiles · social_linksCareer content
experiences · experience_achievements · skills · skill_categoriesPortfolio
projects · project_technologies · education · certificationsPublishing
resume_versions · resume_sections · site_settingsOperations
media · contact_messages · analytics_eventsYou can inspect the code.
The final version contains 60 recorded source files. These examples show public content and secure owner sign-in without exposing secrets or personal data.
src/lib/content-store.tsexport async function getPublishedContent() {
noStore();
return await readByIds([publishedId, "published", "main"])
|| normalizeContent(defaultPortfolioData);
}src/lib/auth.tsconst value = `${payload}.${signature(payload)}`;
cookies().set("ankit_studio_session", value, {
httpOnly: true,
sameSite: "lax",
secure: process.env.NODE_ENV === "production"
});Recorded source snapshot
0007a6ca9a3d…3cebfab6b8bSee what passed—and what didn’t.
The check record was saved on 15 September 2026. Every required check passed, and three moderate heading-order issues remain visible in the report.
100quality score6 of 6 required checks passed
Code check
The TypeScript check completed without errors.
Release build
The production version built successfully in Next.js.
Core journeys
Ten key routes and the health check worked.
Ready to launch
The final preview responded successfully.
Accessibility
Ten routes had no serious or critical issues. Three moderate heading-order issues remain in the record.
Every build. Every release.
Failed attempts stay beside successful ones. The final version was approved, checked, and launched without hiding what happened before it.
23 builds, all recorded
First app version and six updates
5f9827bb ready5e8885dd ready81104109 readye2a950fc ready5e3c62b9 readyb2df2b44 ready9ddfcb3e readyEight checked versions and two failed checks
77c56bb5 ready881b85f9 ready1bd8c254 ready6360b5db ready608a0d76 ready93b7892e readye3c402ce readyb82c9d89 readya6196f8b failed214ccfd6 failedOne approved update
17ddfea3 readyFive checked versions; 498e4df2 became the final release
e44999ed readyc907ef7e ready6189b9a8 readyf63c0cc3 ready498e4df2 readyLaunch timeline
Database change approvedFinal version 498e4df2
Build passedCompleted in 6m 38s
AWS launch succeededHealthy 11m 55s after build start
AWS launch succeededRecorded relaunch
AWS launch succeededRecorded relaunch
AWS launch succeededLatest recorded launch
Custom domain recordedportfolio.entea.in currently returns 404
The record includes two failed builds and two early AWS launch failures. Five later AWS launches succeeded.
We tested the way back, too.
Returning the app to an earlier version and recovering Entea’s own records are different jobs. Both were tested and dated.
AWS rollback worked
An earlier saved version was restored without rebuilding and passed its health check.
AWS launch checks: 8 / 8
Access, runtime, publishing, HTTPS, domain, rollback, safe cleanup, and interrupted-run recovery all passed.
Encrypted platform backup
A 747,490-byte encrypted backup completed with SHA-256 43121ed3…286644a.
Recovery test passed
The encrypted platform backup was checked, restored in a separate space, and recorded successfully.
This backup covers Entea’s own build and control records. It does not cover the portfolio app’s database.
We measured what we could—and said what we couldn’t.
System time is recorded to the second. Human work time was not tracked, so we do not turn clicks or calendar time into a made-up savings claim.
6m 38sfinal build time
11m 55sfinal build to live AWS app
2h 40m 31ssystem time across 23 attempts
28 actions21 database approvals + 7 launch requests
Human work time was not captured for this build. We will not publish an hours-saved claim until a future project records it properly.
Two more builds. Gaps included.
These are internal Entea examples, not customer stories. We show what was built and what was not recorded.
Workforce operations
Enterprise VMS Timesheets
0e7881b1Create a desktop-first Vendor Management System for rapid weekly and monthly timesheet entry, validation, approvals, autosave, and calculated summaries.
DeliveredA complete, archived Next.js app with 29 source files and PostgreSQL database updates.
Recorded time22m 56s recorded build runtime
This early build has no locked quality report or public launch record.
Finance operations
LedgerTrack
fa9d34dcBuild a business expense tracker for recording, editing, searching, filtering, and deleting expenses with PostgreSQL persistence.
DeliveredA complete, archived Next.js expense app with 18 source files and database setup.
Recorded time5m 11s recorded build runtime
This early build has no locked quality report or public launch record.
Bring the brief. Ask for the receipts.
A pilot should leave you with working software and a clear record of how it was made.