Directory & Workspace Admin

Directory and workspace admin features make WyrdOS usable beyond day-to-day execution. They track the resources around the work, define workspace conventions, and control how people and automation access data. Operators use this area to keep the system clean. Buyers use it to evaluate whether WyrdOS can fit into a real organisation.

The directory answers: what tools, people, companies, and funding opportunities does this work depend on? Workspace admin answers: who can access the workspace, how is it configured, and how does data move in or out?

Stack

Stack is the technology and tool inventory. A stack entry can include website, docs link, description, category, subcategory, and relationships to containers.

Use Stack when:

• A container depends on a tool or platform.
• A buyer needs to understand the operational environment.
• A team wants to review tool ownership or fit.
• Integrations or agents need a clean source of tool context.

For example, the Product container might link to analytics, support, or documentation tools used during beta onboarding. That makes tool dependency visible beside the work.

Good stack entries are specific. Analytics platform is weaker than an entry with the actual vendor, URL, use case, and linked container.

Rolodex

Rolodex is the contact and company directory. It can store organisations, people, contact details, points of contact, and social links. It is useful when relationships matter to execution.

Use Rolodex for:

• Customers and prospects.
• Partners and vendors.
• Advisors and funders.
• Internal or external points of contact.

The value of Rolodex is not address-book replacement. The value is linking relationships to operating context. A funding opportunity can connect to a rolodex entry. A container can reference the people or organisations that matter to the work.

Funding

Funding tracks opportunities, eligibility, deadlines, decision timelines, and related entities. It can link to containers, pillars, and rolodex entries. That makes funding part of the operating graph rather than a separate spreadsheet.

Use Funding when:

• Opportunities have review dates or deadlines.
• Eligibility needs to be tracked.
• Funding work supports a strategic pillar.
• Contacts and organisations matter to the opportunity.

For a launch readiness effort, a funding opportunity might link to the Product clarity pillar, the Product container, and a rolodex entry for a funder. That gives both operators and buyers a clearer view of why the opportunity exists and what work it affects.

Categories, Types, And Templates

Settings let teams configure the labels and defaults that make WyrdOS readable. Types and categories are scoped to entity types, so a container category does not need to mean the same thing as a stack category.

Use categories and types to support filtering and review. Do not use them to encode every nuance. If every item needs a unique category, the category system is no longer helping.

Templates define default content for entity bodies and master documents. They are one of the simplest ways to improve quality because they shape what users write at creation time.

Strong conventions:

• Categories are few enough to scan.
• Types describe meaningful operating differences.
• Templates ask for information reviewers actually need.
• Settings are reviewed when the workspace changes shape.

Weak conventions:

• Categories duplicate statuses or priorities.
• Types are used inconsistently across teams.
• Templates become long empty forms.
• Settings are changed without explaining the new convention.

Workspace Settings

Workspace settings cover identity, preferences, billing, integrations, connected apps, imports, exports, API keys, and organisation controls where available. This is where buyers and admins evaluate whether WyrdOS can be safely operated.

Important admin questions:

Not every deployment has the same enterprise requirements. When SSO, compliance, migration, or audit requirements are material to a sale or rollout, confirm the deployment-specific details through support before making commitments.

API Keys And Automation

API keys allow scriptable access to WyrdOS. They are workspace-scoped and should be treated like passwords. Keys can carry read, write, and delete permissions. The safest key is the narrowest key that can do the job.

Use read-only keys for reporting, audits, dashboards, and verification jobs. Use write permissions only when a script needs to create or update records. Use delete permissions rarely, and only when the workflow includes recovery or review.

External agents should usually create evidence proposals instead of directly writing accepted evidence. That keeps humans in control of what becomes part of the trusted operating record.

Imports And Exports

Imports and exports matter for trust because they reduce lock-in concerns and support migration, reporting, and backup workflows. WyrdOS exposes structured data through API and CLI surfaces, and the product includes import/export-oriented settings areas.

Use imports when:

• A workspace starts from an existing spreadsheet or system.
• Funding, directory, or operating data needs to be seeded.
• A migration requires repeated validation before cutover.

Use exports when:

• A buyer needs diligence material.
• A team needs backup or reporting data.
• An admin wants to validate that WyrdOS reflects the expected operating graph.

Import strategy entities before execution entities when possible. It is easier to link containers and zones upward if principles, pillars, and goals already exist.

Example Workflow

For beta onboarding:

1. Define a few product and operating categories.
2. Create templates for containers, zones, and pages so users capture decisions consistently.
3. Add Product-related tools to Stack and link them to the Product container.
4. Add key beta customers, advisors, or funders to Rolodex.
5. Track any launch-related funding opportunities in Funding.
6. Create a read-only API key for reporting.
7. Export or inspect the operating graph before a buyer or leadership review.

This keeps resource context, workspace conventions, and access controls aligned with the work.

What Good Usage Looks Like

Strong directory and admin practice:

• Stack entries identify real tools and their operating role.
• Rolodex entries are connected to work where relationships matter.
• Funding opportunities carry deadlines, eligibility, and links to strategy.
• API keys use least privilege.
• Templates and categories make the workspace easier to understand.
• Import/export paths are understood before high-stakes rollout.

Weak practice:

• Directory entries are unlinked and never reviewed.
• API keys are over-permissioned or shared informally.
• Categories grow until filtering becomes meaningless.
• Funding deadlines live outside the operating graph.
• Buyers hear trust claims that the deployment has not verified.

Trust Notes For Buyers

Directory and admin features build trust by showing that WyrdOS can operate in a real environment. Tools, people, opportunities, categories, templates, access, and data movement are visible enough to review.

The right buyer claim is practical: WyrdOS gives teams structured controls and reference points for operating their workspace. Deployment-specific requirements such as SSO, compliance attestations, retention, or migration guarantees should be confirmed before they are promised.

Automate This

Use these references for automation and admin workflows:

• API keys
• Audit and data controls
• Stacks API
• Rolodex API
• Funding API
• CLI overview