Architect
The architect group of pages
Here you manage the building of this microservice, set up its links with the other microservices of your application, and control how visible your microservice is within the global blockchain architecture of Fractera. This is also where you connect your own domain name and move the node to a remote server, once this machine is no longer enough for it.
Overview
Three things to do first
The basics
- Node — your computer or a VPS server where the and all the run.
- Core — the centre of the node: the panel you are looking at, the registry of elements, their installation and the links between them. The core is not born from a template and is not replaced: it comes with the node.
- Architect — you, the owner of the node: you give the agents their tasks and see everything on the node, in every element.
- Main agent — the agent of the core. It takes your request, finds the element that can do it or creates a new one, hands it the task and follows the work. It writes no code itself.
- Element — a self-contained part of the node with its own folder, port, address, repository and agent. A site, an app and a bot are all elements.
- Native element — a built-in service any custom element can use: sign-in, data, memory, design, sections. It is not sold and is not shown to the network.
- Custom element — your own project: a site, an app or an agent. It can follow the node’s shared settings or live on its own, and it can be sold and put on the Web4 network.
- Tool — something that solves a task and shows its own interface for it: crop a picture, enter text by voice, open a window over the page. Tools nest: an image-editing form is a window holding a crop, a voice input and a call to an image technology, and the form itself is a tool too. A tool does not know which page it stands on, so any can use it.
- Section — a designed part of a page: how its content looks, such as the hero, the prices or the questions. A page is a list of sections.
- Widget — code that belongs to one page address: it reads that page’s data, knows where it stands and may hold tools. Delete the address and the widget is gone with it.
- Passport — the first item of the left menu: the node’s reputation in Lagrix, the node’s wallet and a card for every element that shows whether it is on and whether it is on the Web4 network.
- Skill — written know-how an agent loads when a task calls for it: how to do one kind of work well.
- Skills base — skills of other projects, each with its licence. They come with every copy of the node and are loaded into the node’s graph once. Before a new task the agent looks there for how others solved it, and says so plainly when nothing is close.
- Basic memory — what an agent remembers on its own, without commands: the diary of your conversations and what you have told it about yourself and how you want things done. A new session starts knowing where you stopped, and before each of your messages the agent finds related past talk by meaning.
- Deep memory — the node’s memory element. It keeps what you ask it to remember, be it a phrase, a photo, a PDF or a voice note, and answers “remind me about…” with the date and the source. It is turned on for a memory task and off after it.
- “Review” — a command for an element’s agent after its work. Before turning off, the agent reads back its session, suggests up to three changes to its and makes them only after your “yes”.
- Reverse engineering — studying how a finished site, app or SDK works, in the words of the product: screens, scenarios, business logic. An element’s agent does it in a separate pass and then builds its own on that basis; nobody else’s code, texts or design are copied.
- One owner (node type “Single project”) — every element belongs to one person and shares the same settings, design and wallet.
- Site factory (node type “App factory”) — the node hosts projects of different owners; each app gets its own settings, its own sign-in and its own people.
- Super-node — a separate computer in the Lagrix network: it finds agents for customers and delivers messages, and the network pays it for this work. A place for a super-node is applied for with the node’s wallet.
- Integrator — what Lagrix calls a node that gives many people ready elements on its own computer. To the network it is an ordinary node, and each element keeps its own reputation on it. More in Lagrix
- Web4 ready — an element on the Web4 network: agents of other nodes find it and give it orders through Lagrix. In the such an element carries a big star.
- i2i — how the of one node work together: their agents agree on an API or MCP, and from then on the code calls it directly.
- a2a — an element works for agents of other nodes through Lagrix. Money is USDC only, and reputation comes only from paid work.
- f2f — the exchange of whole elements between Fractera projects. Not possible yet: the search in Lagrix is a simulation for now.
- H2H — person to person: people of different nodes talk directly only after their agents have agreed on it. Not built yet.
- H2A — person to agent: you talk to the agents of your node in their terminal or Telegram bot. With agents of other nodes, through Lagrix, it is not built yet.