Injext.

The idea

Many software changes are familiar: add authentication, add a database table, wire up a new route. Each one reaches through several layers of an application, and doing it by hand, or asking an assistant to improvise it each time, repeats the same work with new chances for error.

Injext treats a familiar change as a reusable operation. The plan is visible before anything is written, the changes are recorded, and the original files can be restored. The aim is to keep a developer's attention on the idea rather than the plumbing.

How it works

Injext first reads the project: its framework, entry point, server structure and template. The same mutation then takes a different shape in each supported stack. The planner separates the change into specific file operations across the interface, server, database and configuration layers. The patcher applies them, and a ledger records what was done. The rollback engine keeps backups of every modified file.

A captured run: adding authentication

The exhibit replays real output from the add-auth mutation, version 0.4.0, run against two small, disposable fixtures:

• Express: 8 operations, 3 files created and 2 modified.
• Replit full stack: 17 operations, 6 files created and 4 modified, across the interface (a sign-in page, session hook and route guard), the server (authentication routes and JWT middleware), the database (a user table in the shared Drizzle schema) and configuration (dependencies and environment placeholders).
• Rollback: in both runs every created file was removed, every original file matched its original contents, and the application ledger was empty.

The 3D exhibit on Media Bishop

The exhibit is an assembly chamber in five beats: Intent, Read, Plan, Assemble and Restore. A faceted amber core represents the intent. A scanning plane reads the stack, the layers separate, and each changed file becomes a module suspended over its destination. Visitors can switch between the Express and Replit stacks, select a layer, and open the actual captured code for every file, before and after.

The browser replays the captured run. It does not run Injext or modify anyone's repository, and the fixtures were not deployed or tested as working authentication services.

Status

Injext is a prototype. Token savings and compatibility with more editors and stacks are goals still to be validated, not established results.