Choosing a Legacy Travel Cohort That Treats Your Skills as Real-World Capital

Legacy travel cohorts are popping up everywhere — programs that promise you can work remotely while building something meaningful. But most treat your skills like a side gig, not real capital. Here's what to look for.

Where Legacy Travel Cohorts Show Up in Real Work

Startup retreats vs. legacy residence programs

The difference shows up fast. At a startup retreat, you trade two weeks of code for equity that vests over four years — or maybe a flat fee and a nice photo with the founders. Legacy residence programs flip the script. You arrive with a skill set — writing, sysadmin work, product design — and leave with a stake in something that outlasts the Wi-Fi password. I have watched a writer negotiate partial IP rights to a program's internal newsletter archive; she now collects a small royalty every quarter. That's not a stipend. That's ownership. The catch is context: retreats optimize for speed, residencies for asset-building. One hands you cash. The other hands you a key.

Most teams skip this: they assume any work-trade arrangement counts as legacy. Wrong order.

How skills become equity or reputation

Skills mutate depending on the container you drop them into. A photographer who documents a residency's daily life might receive nothing upfront — but the images become part of the program's permanent branding, and her name appears on every brochure. That reputation compounds. A programmer who builds a booking system for a remote cohort gets shares in the operating entity, not a freelancer invoice. I have seen this work exactly once without friction: the code was modular, the agreement was notarized, and the cohort ran for eighteen months. What usually breaks first is the handshake that never got written down. Skills turn into capital only when the terms are explicit — not when everyone nods over a beer.

'I spent two years building their internal tools. When I left, I had zero equity and a notebook full of screenshots. Never again.'

— ex-resident, three cohorts ago

Case: the programmer who traded code for shares

She joined a long-stay program in coastal Portugal. The deal: rewrite their clunky booking platform in exchange for 2% equity in the retreat company. Nine months later, the platform handled 40% more bookings with half the support tickets. But here is the pitfall — when the cohort structure itself killed momentum. New residents rotated in every six weeks, each wanting custom features. The roadmap bloated. Her equity stake diluted after a second funding round she had no vote on. The lesson? Legacy arrangements need governance, not just a percentage. You want a board seat or a veto on scope creep. Otherwise your skill becomes free feature labor.

That hurts.

When cohort structure kills momentum

The very design that makes a cohort valuable — fixed start dates, rotating participants, shared resources — can strangle the work-trade model. A designer who joins mid-cycle inherits decisions made before arrival. A developer who finishes a module only to see the next cohort ignore it. I have watched three teams revert to simple stipends because the overhead of tracking who-owes-what-equity became unmanageable. The fix is not to abandon the model. It's to cap the cohort size, define the deliverable in one sentence, and separate the maintenance role from the innovation role. Otherwise you get drift, resentment, and a spreadsheet nobody opens.

Foundations Most People Get Wrong

Confusing Activity With Capital Accumulation

Most teams mistake motion for momentum. They pack a cohort calendar with stand-ups, whiteboard storms, and Slack threads—then call it 'legacy work.' I have watched people log sixty-hour weeks on a cohort project, only to discover their output died the moment the group disbanded. That hurts. Busywork feels productive in the moment—it silences the anxiety of 'am I contributing?'—but it rarely compounds. The true test is simple: if nobody would pay to re-run your process next quarter, you built activity, not capital.

One travel cohort I joined spent three months building a shared spreadsheet of 'hidden hostels.' Everyone contributed rows. Great collaboration, right? Wrong order. The sheet had no verification system, no update cadence, and no owner. A year later, half the entries were outdated. The real capital was the trust we built during late-night edits—but we never documented how to sustain that. We confused a flurry of tabs with lasting infrastructure.

The catch is that activity feels like progress. Legacy capital is boring. It's the single script that auto-fixes visa date formats. It's the one-page onboarding doc that saves new members four hours. That stuff doesn't flash on a dashboard.

The Difference Between Portfolio Projects and Legacy Assets

Portfolio projects are résumé bait. You finish them, present them, and move on. Legacy assets, by contrast, pay out repeatedly without your active presence. Most people skip this distinction until a cohort's work dissolves the week after the final presentation. A portfolio project might wow a hiring manager; a legacy asset changes how your cohort makes decisions six months later.

I once built a 'trip-cost calculator' inside a travel cohort. Pretty spreadsheet, lots of formulas. Felt like a portfolio win. But nobody used it after month two—the exchange rates shifted, the formulas broke, and I was too busy to fix it. That was a portfolio project dressed as an asset. A true legacy asset would have been a simple, version-controlled script that pulled live currency data. Boring. Durable. Harder to show off in an interview, but it would have earned trust from the group every week.

Worth flagging—cohorts that treat every deliverable as a portfolio piece produce beautiful graveyards. You get polished PDFs that gather dust. The trick is to ask: 'Does this reduce future work, or just prove past work existed?'

Legacy isn't what you made. It's what keeps working after you stop showing up.

— Cohort lead, Southeast Asia travel collective

Why 'Network Effects' Are Often Just Acquaintances

Everyone wants network effects. Few admit their 'network' is a stack of LinkedIn connections who never reply. In travel cohorts, the mistake is assuming any collaboration produces lasting value. It doesn't. Real network effects need recurring, high-friction interactions—shared risk, joint problem-solving, or co-ownership of something fragile. Casual coffee chats? That's acquaintances. That's noise.

Flag this for luxury: shortcuts cost a day.

Flag this for luxury: shortcuts cost a day.

I have seen cohorts celebrate '50 members in the Slack' as if density equaled value. Then someone posts a genuine request—'I need a couch in Bangkok next week'—and gets two replies, both wrong. The network didn't have effect; it had surface area. The teams that fix this impose a cost to entry: you must contribute a verified piece of local knowledge before you can ask for help. Suddenly, the network tightens. The acquaintances either step up or step out.

So the foundation most people get wrong is simple: they treat collaboration as the goal, not the raw material. Collaboration without a structured feedback loop—where bad contributions get flagged and good ones get reused—produces friendship, not legacy. Friendship is fine. But it won't book you a room in Ulaanbaatar when your phone dies.

Patterns That Actually Deliver

Co-ownership structures and IP split agreements

Most teams skip this: the legal chassis. They sign a standard LLC or a simple partnership, then wonder why the designer feels like a contractor and the engineer carries resentment. I have seen a cohort fail in six months because the IP clause read “all work product belongs to the company.” The company was three people who hadn’t defined what “company” meant. The fix was a split-ownership schedule — 25% to each founder, 25% held in trust for future contributors, 25% reserved for the cohort’s next project. That trust piece mattered. It turned individual code and copy into a shared durable asset, not a hostage situation. The catch is that lawyers hate drafting these unless you pay for bespoke work. Worth it. One cohort I advised used a simple three-page agreement that granted each contributor a non-exclusive license to their own output, while the cohort held exclusive rights to the combined product for eighteen months. After that? Rights reverted. The cohort dissolved cleanly. That never happens with boilerplate.

Wrong order. Most people start with the mission statement. Start with the exit terms.

“We built the thing, then we built the prison. Next time we’ll build the prison first so we know where the doors are.”

— Lead engineer, legacy travel cohort that split after eight months

Skill-specific cohorts (design, engineering, strategy)

Generalist cohorts sound noble. They rarely deliver. I have watched a group of five people — two engineers, one designer, one marketer, one domain expert — spend three months arguing about what “legacy” meant. Each person brought a different assumption about speed, quality, and ownership. The designer wanted polish; the engineer wanted modularity; the marketer wanted a launch date. Nobody was wrong. Everyone was stuck. The pattern that actually works is skill-specific cohorts: all engineers, or all designers, or all strategists who have already solved their own craft problems and want to apply them to travel infrastructure. A cohort of three senior Rails developers, for example, can rebuild a booking system for a rural lodge in four weeks. They speak the same language. They judge output by the same standards. The trade-off is narrow scope — you can't suddenly pivot to marketing or operations without recruiting a new skill group. But narrow scope is what produces durable assets. The lodge gets a system that works, not a prototype that stalls.

Most teams revert because they want diversity too early. Diversity of skill is a runtime property, not a design-time one.

Time-boxed sprints with deliverable milestones

Open-ended collaboration is a polite word for drift. I have seen cohorts burn twelve weeks on research that could have been compressed into two if someone had set a hard boundary: “We ship a working API on Friday or we scrap the feature.” Time-boxed sprints solve the infinite-iteration problem. But the trick is the milestone conditions — not just dates. Each sprint must produce something another person can use without the original author present. That's the durability test. If the engineer falls sick, can the designer pick up the config file and deploy? If no, the sprint failed even if the code compiled. One cohort I worked with enforced a rule: every two-week sprint ended with a public demo and a written summary that a new contributor could read in ten minutes. The summaries became the cohort’s real documentation. The demos surfaced bad assumptions early. The cost was overhead — about three hours per sprint for writing and rehearsal. But that overhead saved them from the typical pattern: six months of work, then a single handoff email that nobody reads.

What usually breaks first is the time-box itself. A sprint ends. The output is ugly. Someone says “just one more week.” That's the inflection point. Let it slide once and the cohort becomes a perpetual beta.

Peer review that treats output as public goods

Private feedback loops create private standards. Public review forces the cohort to justify its decisions to strangers — and strangers are brutal in a useful way. I have seen cohorts adopt a lightweight pull-request culture even for non-code work: design files, strategy documents, even travel itineraries. Each submission gets two required reviewers, one from inside the cohort and one from outside. The outsider can't be a friend. They must be someone who will use the output, or someone who has built something similar and knows where the seams blow out. The result is not just better work. The result is shared vocabulary. When a designer explains a layout decision to an engineer who reviews the spec, both learn the constraints that the other faces. That mutual understanding becomes a social asset — hard to copy, impossible to buy. The pitfall is review fatigue. After the third week, people start rubber-stamping. The fix is to rotate reviewers and cap review requests at one per person per week. Scarcity makes reviews honest.

One concrete anecdote: a cohort building a trail-mapping tool required every route submission to include a field-test log. The reviewer (an outsider from a different cohort) rejected a route because the log showed three water crossings without safety notes. The submitter was annoyed. The route got fixed. Six months later a traveler used that route in monsoon season and avoided a flash flood. That's the public-goods argument — not abstract. It saves a life. Or at least saves a pair of wet boots.

The next experiment: try running one sprint where all reviews are public. No private DMs. No hallway negotiations. Watch how fast the output improves, and how fast people either commit or leave.

Anti-Patterns and Why Teams Revert

The 'we'll figure out ownership later' trap

Most teams skip this: deciding who holds the keys when the cohort ends. They launch with shared Notion docs, a collective bank account, and warm feelings about 'co-creation.' Then someone needs to sign a contract for a client project that uses the group's codebase. Or the LLC question surfaces. Or a visa sponsor demands a single legal entity. What happens? The cohort fractures into standard coworking—everyone on their own laptop, no shared risk, no shared upside. I have watched three promising groups dissolve within weeks because nobody wanted to have the awkward equity conversation on day one.

Fix it on arrival. Not later.

The catch is that ownership talks feel premature when you haven't built anything yet. But the alternative is worse—you build something, then fight over who owns what. One concrete fix: a one-page 'legacy memo' drafted before the first group project, stating how IP, revenue, and decision rights distribute upon exit. It doesn't need to be legally bulletproof. It needs to exist. Without it, the cohort reverts to tourism with laptops.

Domination by a single charismatic founder

Here is the pattern that kills more cohorts than any other: one person with a louder voice, a stronger network, and a habit of saying 'I'll handle it.' Everyone else relaxes. The founder pitches, the founder closes clients, the founder decides what the group works on next. That feels efficient for about three months. Then the founder burns out, or moves to another city, or simply stops carrying the weight—and the group evaporates. I have seen this happen inside a six-month window twice, and both times the remaining members admitted they had stopped contributing weeks earlier.

Not every luxury checklist earns its ink.

Not every luxury checklist earns its ink.

Worth flagging—this is not malice; it's gravity. Charisma pulls responsibility toward itself.

The anti-pattern is structural, not personal. Rotate the lead role every two weeks. Hard schedule, no exceptions. Each rotation forces quieter members to practice pitching, negotiating, or shipping. The cohort survives because no single person becomes the bottleneck. That said, some groups resist this because it slows down execution. They trade speed for fragility. The question is whether you want a fast collapse or a slow build.

Burnout from constant pitching without building

Another common wreck: the cohort spends 70% of its energy on internal demos, pitch nights, and 'synergy sessions.' Everyone talks about what they could build together. Nobody actually writes the code, stitches the deck, or ships the deliverable. The energy feels productive—lots of whiteboards, lots of excitement. But after three weeks there is nothing to show except a shared Google Drive full of meeting notes. The cohort becomes an expensive social club.

'We spent six weeks aligning on a vision. Then we had nothing to align on because we never built anything.'

— former participant, remote cohort, 2023

The fix is brutal: by the end of week one, ship something—even a single public post, a simple prototype, or a client intro email. Building forces decisions that conversation avoids. If the group can't produce a tangible output in seven days, the premise is wrong. They're not a legacy cohort; they're a book club with ambition.

Why many cohorts dissolve within 6 months

Most teams skip maintenance planning until it's too late. The first two months feel like a visa-fueled adrenaline rush—new city, new collaborators, new workflow. Then the novelty fades. Someone's freelance contract ends. Another member gets a full-time offer. A third realizes the group's skills don't actually complement each other in the market. The cohort drifts into parallel solo work, then silence, then a Slack message: 'Hey all, I think I need to focus on my own projects for a while.'

That hurts. Not because it's unexpected, but because it was avoidable.

The anti-pattern here is assuming the cohort's value is self-sustaining. It's not. The structure needs explicit renewal rituals—weekly check-ins about who is still committed, a shared revenue target that resets each month, and a hard rule that any member can call a 'legacy audit' where the group decides whether to continue or disband cleanly. Without these, entropy wins. I have seen it happen in exactly five months, fourteen days, and one unread message. Don't let your cohort become that statistic.

Maintenance, Drift, and Long-Term Costs

Keeping IP Agreements Alive After Members Leave

A legacy cohort isn't a weekend camping trip. You have to know this going in: people will leave after 6 months, 2 years, or when a better offer lands. What happens to the shared intellectual property then? Most teams skip this—they draft a simple co-ownership clause and assume it holds. It doesn't. I have watched a perfectly functional travel cohort unravel because a departing member claimed exclusive rights to a client relationship they'd built using the cohort's shared reputation. The legal workaround? A sunset clause that converts full IP ownership into a revenue-share license once someone exits. That sounds fine until you need a lawyer to renegotiate it every time. Worth flagging—one cohort I advised spent $4,000 annually just keeping those agreements updated. Not a fortune, but it eats your margin in a way nobody budgets for.

IP drift is slower. More insidious.

Reputation Decay When the Cohort's Output Stagnates

The catch is that a cohort's reputation compounds fast at first, then flatlines. You launch strong—three consulting gigs, a joint workshop, a small press mention. Then six months pass. No new output. The shared blog goes silent. The member who used to curate the project gallery gets busy. Outsiders stop checking. That hurts more than you think: the cohort's value to your next client is partly the halo of *recent* work. Stale projects signal "we used to be a thing." I have seen a cohort lose a $12,000 contract because the lead client googled the group's last public deliverable—it was 14 months old. The fix is boring but real: assign a rotating "output steward" for 90-day sprints. Not a glamorous role. It works because someone is paid to care about the public face.

'The hardest cost to track is the slow erosion of why you all said yes in the first place.'

— former cohort lead, now running solo contracts

Financial Overhead of Shared Legal Structures

Let's talk money directly. A shared LLC or cooperative entity costs more than the filing fee. You need annual state reports, a registered agent, a shared bank account that requires two signatures for every withdrawal. That coordination friction adds up—three people trying to schedule a 30-minute call to approve a $200 expense? That's 90 minutes of cumulative time, plus follow-up emails. Most teams revert because the overhead exceeds the perceived benefit. I have seen a cohort dissolve purely because the quarterly accounting reconciliation took longer than the actual work the group produced. The anti-pattern here: forcing a formal structure too early. Start with a simple contract, not an entity. You can incorporate later, once the revenue justifies the legal drag. Not yet.

That sounds pragmatic. It's. But the real cost is rarely the money.

The shared purpose erodes. Quietly. You meet less frequently. The Slack channel slows from daily to weekly to "I'll respond next month." Someone starts taking individual clients under their own name, not the cohort's banner. Nobody calls it out because everyone is busy. The drift is natural—people's skills grow in different directions, and the original mission that fit perfectly at month three no longer fits at month eighteen. I have no clean fix for that one. You can schedule a quarterly "reset" meeting where you re-read the original cohort charter and ask bluntly: does this still work? Most teams skip it. Then they wonder why the magic faded.

When Not to Use This Approach

If you’re primarily seeking income stability

Legacy travel cohorts are not payroll. They're not a monthly direct deposit that arrives whether you deliver or not. If your rent depends on a predictable check every two weeks, a cohort built on skill-as-capital will feel like standing on a trampoline during a monsoon — bouncy, unpredictable, and occasionally wet. The catch is that most cohorts pay out in tranches tied to project milestones, IP licensing, or shared revenue. That means a four-month dry spell is normal. Even healthy. I have seen talented engineers join a cohort, hit a six-week funding gap, and burn through savings while the team was still aligning on the first deliverable. If you can't stomach a three-month runway with no guaranteed top-up, stay in the W-2 world. That's not a failure. It's a mismatch.

Reality check: name the travel owner or stop.

Reality check: name the travel owner or stop.

If the cohort lacks clear IP or equity frameworks

This is the reddest flag. A cohort that talks about “shared ownership” but has no written vesting schedule, no buyout clause, no IP assignment agreement — that's not a cohort. That's a book club with deliverables. The tricky bit is that many new cohorts pitch the “legacy” label as a substitute for legal rigor. “We’re building something together” sounds warm. It will feel cold when a founding member leaves with the codebase and an NDA that blocks your next three years. Worth flagging—one team we advised had a handshake agreement on a 50/50 IP split. Eight months in, the other party took a full-time role and ghosted. No contract, no recourse. If the cohort can't produce a one-page framework for who owns what, walk. Don't negotiate. Walk.

“A cohort without IP guardrails is a rental with a deposit you never see again.”

— freelancer who joined three “legacy” collectives in two years

If you’re unwilling to invest in legal basics

Most people skip this. They assume the cohort lead has handled it, or that good faith will carry the group through a dispute. Good faith breaks on Tuesday at 2 PM when revenue hits the bank account and two people claim the same deliverable. You need three things before you ship a single line of code or write a single client email: a simple operating agreement, a clear contribution ledger, and a dispute resolution clause. That sounds like overhead. It's. But a weekend of lawyer time now saves two months of arbitration later. I have seen a cohort of four experienced professionals take six months to unravel a revenue split because nobody had written down how to value “strategy hours” versus “execution hours.” Six months. If that sounds like an investment you can't make — in time, money, or attention — the cohort will cost you more in drift than you earn in capital.

When the ‘legacy’ label is just marketing

The term “legacy” gets thrown around like confetti at a startup funeral. A real legacy cohort treats your skills as long-lived assets, not burnable fuel. A fake one uses the word to justify below-market rates and vague promises of future upside. How do you tell the difference? Look at the money. Real cohorts pay a base rate — even if low — for the work you do today. Fake ones ask you to “invest your time in the vision” while they pocket client fees. If the cohort asks you to work for free for more than one pilot cycle, the label is decoration. Your skills are capital. Treat them like it. If the cohort can't cash them today, don't let them borrow against tomorrow.

Next step: Before you sign anything, write down your minimum three conditions — income floor, IP clarity, legal budget. If the cohort can't meet all three, decline. No exceptions.

Open Questions / FAQ

Can legacy work ever be truly passive?

No — and the people who tell you otherwise are selling courses, not running cohorts. I have watched teams treat a legacy travel story like a vending machine: drop in a skill once, expect indefinite returns. That sounds fine until the repository falls eight months out of sync, or the API that powered your curated map feed gets deprecated. Passive requires periodic attention — think quarterly health checks, not daily grind. The catch is that "periodic" quickly becomes "never" without a calendar trigger. We fixed this by assigning a rotating steward who does nothing except check one metric per month. That single habit kept a cohort alive for three years. But alive is not thriving. The gap between maintenance and growth is where most passive dreams die.

True passivity is a myth. Sustainable, however, is real.

What happens when a cohort member exits?

The exit terms are where most handshake agreements implode. A writer leaves your storytelling cohort — does their contributed route guide vanish from the shared archive? Do they retain the right to republish the same itinerary verbatim on Substack a week later? I have seen a cohort collapse entirely when one member pulled their content, and the remaining three could not reconstruct the narrative flow. The fix is brutal but necessary: treat every contribution as a license, not a gift. Write a one-page exit memo before anyone joins. State explicitly whether the work stays, gets attributed, or evaporates. Most teams skip this because it feels cold. That coldness saves the cohort from dying of resentment six months later.

What about buyouts? If a member departs, does the group compensate them for past work? We tried a simple formula: hours logged × a fixed hourly rate — capped at what a replacement would cost. It felt transactional. It also worked.

Every exit is a stress test. If the cohort survives the first departure, it was never a house of cards.

— former travel-tech founder, after losing two co-authors in one quarter

How do you value non-technical contributions?

Hardest question in the room. A developer writes the scraping pipeline for flight deals — hours are visible, output is measurable. A storyteller shapes that raw data into a narrative that makes readers book tickets — what is that worth? Most cohorts default to "everyone gets an equal share." That works until one person does forty hours in a week while another spends three hours editing comma placement. Resentment breeds silently. Worth flagging—soft skills compound oddly: a single well-placed anecdote can lift a guide's conversion rate by thirty percent, but no dashboard captures that. We experimented with a weighted multiplier system: technical contributions got base hours × 1.0, narrative and editorial work got base hours × 1.3, and community management got × 0.9 plus a flat bonus for every member retained more than six months. Imperfect. But better than pretending all labor is equal.

Is there a minimum viable cohort size?

Three is too few — one person gets sick, and the workload doubles. Seven is too many — coordination overhead eats the creative energy. The sweet spot I keep landing on is four to five. At four, you can absorb one exit without panic. At five, you have enough surface area for genuine skill diversity: someone handles the tech stack, someone writes, someone edits, someone markets, someone does the boring but essential admin. Fewer than four, and you're a partnership, not a cohort. More than five, and you spend more time scheduling calls than shipping work. The anti-pattern is scaling before you have a repeatable rhythm. Start with four. Prove the loop. Then ask whether your sixth person adds leverage or just noise.

Summary and Next Experiments

Three criteria for vetting any cohort

You can read every manifesto and interview ten alumni—still won’t tell you whether your skills earn real weight inside the group. I have watched brilliant engineers join cohorts that treated them as glorified ticket-takers. The fix is blunt: demand three signals before you hand over a deposit. First, are there structured skill-gaps documented in the cohort’s charter—actual lists of what the team needs, not vague “we value diversity of thought”? Second, do members rotate into leadership roles based on demonstrated competence, not tenure or charisma? If the same three voices dominate every decision, your capital stays locked. Third, is there a formal mechanism to price contributions—something like a points system or a public ledger of who fixed what? No ledger, no leverage. That hurts.

Most teams skip this until month six. By then the pattern is baked.

A 30-day trial framework

Run a short experiment instead of signing a year-long pledge. Pick one concrete skill you own—deployment automation, contract negotiation, whatever—and offer to solve a specific problem the cohort faces. Do it publicly. Track two things: how quickly the group adopts your output, and whether they credit you by name or absorb the work into the collective. I have seen a brilliant sysadmin run an entire migration for a cohort, only to hear “the team handled it” in the retrospective. That seam blows out fast. The catch is you need to define success before you start. “I want my solution used in production within two weeks” is a test. “I want to feel valued” is a mood. One predicts the future; the other is astrology. After thirty days, ask yourself one question: did my skills change how this cohort operates, or did I just fill a gap they would have outsourced anyway?

Wrong answer? Leave. No guilt.

What to build before you commit long-term

Before you go all in, construct a small reputation artifact that exists outside the cohort—a public case study, a reusable tool, a documented process that other groups can adopt. Why? Because legacy travel cohorts drift. The people who vetted you leave. The charter gets rewritten. The budget shrinks. If your only proof of contribution lives inside a Slack archive or a shared drive, you own nothing portable. Build something that earns you a reference, a blog post, or a consulting call—independent of whether the cohort survives. Not selfish. Defensive. The tricky bit is that this artifact also acts as a forcing function: if the cohort blocks you from sharing work publicly, that's a red flag bigger than any mission statement.

“The cohort that treats your skills as capital will help you export them. The cohort that treats you as a resource will hoard everything.”

— former lead at a now-defunct travel collective, 2023

Start this week. Pick one deliverable you already own, reframe it as a reusable asset, and offer it to the cohort on a thirty-day trial. If they run with it, great. If they ghost you, you learned more than any FAQ could teach. That's the experiment.