Why? Multi-tenant environments. First, we need to understand a few differences between environments:
So
Most people physically separate their tenancy, such as Claude Code, from their personal vs. work laptops. So in most cases, it's not a big deal.
But when you need multi-tenancy, it becomes super stressful. For example, say you have two different toolkits:
Most MCP auth states or code harnesses don't support profiles, so you can only log in to one.
So therefore... a natural evolution was to have both:
to physically isolate tenancies.
Now we've solved the multiple-profile issue, but the client's problems persist. Now let's get back to the environments:
All MCP auth or toolkit auth info should always be saved in the Agent Runtime Environment IMHO. However, a surprising number of harnesses tie them to the LLM server (such as Codex Apps or Claude.ai Plugins) or put them in the end-user UI (Claude Desktop or Codex Desktop).
Now the problem is:
The only way to reliably isolate different auth information is thus:
Then
are both isolated VPS, and
This way, you can provide different toolkits, creating multiple dev environments.
sudo apt update && sudo apt install git && /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" && echo >> ~/.bashrc && echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)"' >> ~/.bashrc && eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)" && sudo apt-get install build-essential && brew install gcc btopshortest path, negative possible.
OPT[v,k]=min(OPT[v,k−1],OPT[u,v]+w(u,v))The set of vertices reachable from source s in the residual graph is one part of the partition. Cut capacity cap(A,B)=∑out Ac(e).
∣f∣=e out of X∑f(e)−e into X∑f(e)Given (G,s,t,c∈N+), start with f(u,v)=0 and Gf=G. While an augmenting path is in Gf, find a bottleneck. Augment the flow along this path and update the residual graph Gf. O(∣f∣(V+E)).
Ford-Fulkerson, but choose the shortest augmenting path.
For any flow f and any (A,B) cut, ∣f∣≤cap(A,B). For any flow f and any (A,B) cut, ∣f∣=∑f(s,v)=∑u∈A, v∈Bf(u,v)−∑u∈A, v∈Bf(v,u)
To reduce a problem Y to a problem X (Y≤pX) we want a function f that maps Y to X such that f is a polynomial time computable and ∀y∈Y is solvable if and only if f(y)∈X is solvable.
Describe how to construct a flow network. Claim "This is feasible if and only if the max flow is …". Prove both directions.
If a standard problem and its dual are feasible, both are feasibly bounded. If one problem has an unbounded solution, then the dual of that problem is infeasible.
| P\D | Feasibly Bounded | Feasibly Unbounded | Infeasible |
|---|---|---|---|
| Feasibly Bounded | Possible | Impossible | Impossible |
| Feasibly Unbounded | Impossible | Impossible | Possible |
| Infeasible | Impossible | Possible | Possible |
To reduce a decision problem Y to a decision problem X (Y≤pX), find a function f that maps Y to X such that f is poly-time computable and ∀y∈Y is YES if and only if f(y)∈X is YES.
Show X is in NP, Pick problem NP-complete Y, and show Y≤pX.
컴퓨트로늄(computronium)은 계산을 수행하는 데 최적으로 설계된 가상의 물질이다.
쉽게 말하면, “물질을 최대한 컴퓨터처럼 만든 것”이다. 일반 컴퓨터는 실리콘 칩, 전선, 냉각 장치, 케이스처럼 계산에 직접 쓰이지 않는 부분이 많다. 컴퓨트로늄은 그런 낭비를 극단적으로 줄이고, 물질의 질량·에너지·구조 전체를 계산에 쓰도록 만든다는 개념이다.
예시로는 다음이 있다.
이 개념은 주로 SF, 미래학, 인공지능 이론, 트랜스휴머니즘, 우주공학적 상상에서 나온다.
핵심은 이것이다.
컴퓨트로늄 = 계산 효율을 극한까지 높이기 위해 재구성된 물질
현실에 아직 존재하는 물질 이름은 아니다. 물리학적으로 가능한 한계, 열 방출, 에너지 공급, 정보 저장 밀도 같은 제약 때문에 실제 구현은 가설 수준이다.
sudo apt update && sudo apt install git && /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" && echo >> ~/.bashrc && echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)"' >> ~/.bashrc && eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)" && sudo apt-get install build-essential && brew install gcc btop