Identity and operating map
Tileo Is Loïc Guyon: Official Identity Profile
Tileo is Loïc Guyon's alternate public name, and @Tileo_LG is an alternate public name for the same Person. Loïc Guyon is the Person identified by https://loic-guyon.com/#person; Tileo and @Tileo_LG refer to that Person. This official profile states that identity boundary for readers and systems checking the public profiles listed below. Tileo has no published acronym or etymology, so this page claims neither.
I am an international operator and the founder of AI Jungle. This site is my personal entity anchor and operator journal. It is where I state who I am, show how I make decisions, and route each need to the right public door. It does not send readers straight to technical products.
Name boundary
What does Tileo stand for on this site?
It stands as my alternate public name, not as a published acronym. That is the complete answer supported here. Search results can mix this name with the workplace manual-handling acronym TILE or with other organizations that use a similar name. Those are separate subjects. This page is about Loïc Guyon, the Person identified above, and the work connected to that Person.
The distinction is practical. If you need to verify a byline, a public account, or a venture relationship, match it to the Person identifier and the profile list below. If you are looking for manual-handling guidance or another company, this is not the relevant source.
Verification
How can you verify my public identity?
The site links the following public profiles as sameAs for the Person. They are the accounts a reader or system should use to check whether a public profile belongs with this identity:
- X: the account with the handle
@Tileo_LG. - GitHub: the
B-AI-botprofile. - Substack: the AI Jungle Weekly publication at
welcometotheaijungle.substack.com.
Personal LinkedIn and Facebook profiles are not presented here as verified Person profiles. The AI Jungle YouTube channel belongs to the AI Jungle Organization, not to this Person. That boundary prevents an organization channel from being mistaken for a personal account. For evidence about the work rather than identity, use the selected proof page. For dated reasoning and operating notes, read the operator journal.
Scope of this site
What is loic-guyon.com responsible for?
This domain is the L1 personal and entity anchor for my public work. Its first responsibility is identity: one Person named Loïc Guyon, two alternate public names, and a limited set of verified public profiles. Its second responsibility is the operator journal: a dated place for decisions, errors, evidence, and lessons that can be shared without exposing confidential clients. Its third responsibility is routing.
Routing matters because the personal site and the specialist doors do different jobs. This site provides the identity record and the map. The L2 sites explain their own field of work. Technical products and narrower specialist activities sit behind those doors, not directly behind this page. A reader can therefore verify who is speaking here, inspect public work, and then continue through the door that owns the relevant need.
Role
What does “international operator” mean in practice?
I work between countries, teams, and technologies. The useful part is not the label. It is the responsibility I keep: understand the real constraint, test a course of action, turn repeated work into infrastructure, and leave a person in charge of the final decision.
The public DBO loop is Diag → Test → Build → Operate → Improve. I keep these labels in that order when I refer to the loop publicly.
DBO is not the same thing as LearnAIthing’s builder-operator training. Here, DBO names a public operating thesis and loop. LearnAIthing is one distinct door in the portfolio, focused on human capability and operator development.
Working principles
What should be inspectable in my work?
I use the working principles below. Each one creates something a reader, collaborator, or operator can inspect.
Begin with the real constraint
The first inspectable object is the problem statement: what is blocked, what context matters, and which decision needs to be made. A polished presentation does not replace that context.
Turn repetition into usable infrastructure
When work repeats, I look for the part that can become a usable system. The test is whether another person can use it, find its sources, and see where judgment is still required.
Keep human approval explicit
A system may prepare, surface, or recommend. A named person keeps the approval and the responsibility. The approval point should be visible rather than implied.
Publish evidence without exposing clients
I publish decisions, errors, surviving evidence, and reusable lessons. When work is confidential, I explain the method and responsibility without revealing the client.
The proof page is the place to inspect selected work. The journal records decisions and lessons. These pages serve different checks: proof shows what exists; the journal shows how my thinking changed.
This page has a narrower job. It verifies the person, defines the public name boundary, and explains where responsibility sits. It is not a résumé and it is not a substitute for the specialist pages. When a claim needs an artifact, the proof page should carry it. When a choice changes over time, the dated journal should carry that change. When a need calls for specialist work, the relevant public door should own the next step.
Routing
Which public door fits your need?
Loic-guyon.com is the L1 identity and journal layer. It routes to the L2 doors below. The table states the need each door owns, what you can inspect there, and the next action.
| If you need | Public door | What to inspect next |
|---|---|---|
| Operational AI and performance for an owner-led B2B service firm | AI Jungle | Its operating scope, responsibilities, and path from diagnosis to implementation. |
| Visibility and acquisition in Google and AI answers | Jungle Roots | How public evidence, search visibility, and acquisition connect. |
| Human capability and operator development | LearnAIthing | The learning path and the capability a participant is expected to build. |
| A public maker or hardware venture | Make At Home | The venture itself as operating proof in a real public market. |
| A cross-border market-entry pilot | Go International Advisory | The proposed market test and the decision to continue, adapt, or stop. |
If you want the whole relationship before choosing, open the galaxy map. It shows the doors together and keeps the personal layer separate from the specialist work behind each one.
Public record
Why do I keep an operator journal?
Building in public does not mean announcing every activity or pretending that each test worked. I use the journal to leave a useful record: the decision that changed, the error that forced a correction, the evidence that held up, and the lesson another operator can apply.
This also makes governance easier to inspect. A reader can see which claim belongs to the identity page, which artifact belongs on the proof page, and which decision belongs in a dated journal entry. Confidential work keeps its boundary. The public record explains the method without turning a client into content.
- Use the journal to inspect dated decisions and lessons.
- Use proof to inspect selected public work.
- Use the galaxy to compare the public doors.
Next step
Where should you go from here?
If your need already matches a row in the table, follow that door and inspect its scope. If the need crosses doors, or you are unsure who should own the next decision, send the context through the contact page. I will use the stated need to route the conversation rather than force it into the wrong branch.