Your display name in the Cioré HQ server should follow this format so the team knows who you are and how to support you:

This helps every contributor and the founder instantly recognize who they are talking to and what kind of work you do. It also helps project managers reach the right people quickly.

If you already have a Discord account, use the per-server profile feature so your changes only apply to Cioré HQ and do not affect your other servers.

Please take a few minutes to make sure your server profile is set up completely. A complete profile helps the team communicate with you respectfully and efficiently.

Use the guide below to choose the correct shorthand for your time zone. Meetings are generally scheduled in Central Time (CT) because that is the founder's home time zone. Use a time zone converter to find the equivalent time in your location.

Your DM preference tells other contributors how to reach you. Please choose the option that fits your comfort level and make sure it is reflected in your server profile.

There is no wrong choice. Choose whatever feels most comfortable for you and your working style.

Contributors can add their pronouns to their server profile so the team can address them correctly and respectfully. Please take a moment to add yours.

• she / her
• she / they
• they / them
• he / him
• he / they

Cioré HQ is the name of our Discord server. Think of it as our virtual headquarters — the place where contributor activity lives, conversations happen, and the team stays connected. Just as the Contributor Hub is where you go to read and learn, Cioré HQ on Discord is where you go to communicate and collaborate.

If Discord is new to you, here is a quick breakdown of how it is organized:

• Some channels are announcement-only — you can read but not post.
• Some channels are project-specific — focused on active initiatives.
• Some channels are role-gated — only visible or accessible based on your contributor role.

• Use the left sidebar in Discord to move between categories and channels.
• You can collapse and expand categories by clicking the category name.
• When looking for a specific channel, check the server map or channel guide if one is available.
• To stay updated, always check announcement channels first — that is where important notices live.

When you first join, head to the Welcome or Announcements channel. That is where important updates, reminders, and notices are posted. Start there, read through what is available, and then explore the rest of the server at your own pace.

Every channel has a purpose. Here are the ones you should know about right away:

We are a distributed, globally connected team. That means communication across time zones, backgrounds, and schedules. Please keep these expectations in mind as you participate in Cioré HQ:

• Before messaging someone, take a moment to check their role, pronouns, DM preference, and time zone in their server profile.
• Please be respectful of how people identify and communicate. Use correct names and pronouns.
• Be considerate of different time zones and response windows. Not everyone is available at the same hours.
• Meetings are scheduled in Central Time unless otherwise noted. Use a time zone translator to confirm your local time.
• Use channels for their intended purpose whenever possible. If you are unsure where something belongs, ask in a general channel or check the server map.
• When in doubt, default to respect. This community is built on care, intentionality, and mutual support.

You have made it. Whether you are an engineer, designer, strategist, writer, researcher, or organizer — you are now part of a team building something that has never existed before. We are creating privacy-first, ethically made, sustainable technology powered by a community that believes technology should serve people, not harvest them.

Your presence here matters. No contribution is too small. Your ideas, perspective, and specific kind of genius are exactly what this team needs, and we are glad you chose to bring them here.

By the time you are reading this page, you have already completed most of the onboarding process. Here is a look at the full journey from start to where you are now, and what comes next.

Now that you are fully onboarded, here is exactly where to focus your energy.

If you have not yet introduced yourself in the Discord introductions channel, use this as your guide. Make it your own — we want to hear your personality, not a form. This is your moment to say hello and let the team start getting to know you.

Cioré runs on clear, direct communication. Here is how to know who to reach and where to go for different kinds of questions.

• For project-specific questions, reach out to the project manager or listed point of contact on the Progress tab.
• For general onboarding questions or if you are unsure where to start, message the founder on Discord.
• Check the Progress tab regularly to stay aligned with what the team is actively building and where support is needed.
• Some opportunities are ongoing project roles. Others are one-off support needs. Each item on the Progress tab should have a contact listed so you always know who to reach.
• When in doubt, over-communicate. We would always rather hear from you than have you sit in uncertainty.

We ask every contributor to operate with ownership, intention, and care. You do not have to be available around the clock, but we do ask that you show up consistently, communicate clearly, and align your work with the mission.

• Read the internal contributor hub so you understand what we are building and how things are organized.
• Ask questions early and often — in shared channels, not in silence. There are no wrong questions here.
• Align your work with the Cioré mission and values. If you are unsure whether something fits, ask first.
• Operate with ownership: be proactive, be transparent, and follow through on commitments.
• Treat every contributor, collaborator, and team member with the same respect you would want to receive.

Because we are building sensitive, mission-critical technology, confidentiality and a respectful environment are non-negotiable. Every contributor is expected to honor these standards.

• All work produced for Cioré is internal company property and must not be shared outside our ecosystem without explicit permission from the founder or designated communications lead.
• Code, CAD files, research documents, internal strategy, and anything shared in the contributor hub must be kept private.
• Public posting about unreleased features, designs, or internal updates is not allowed unless specifically approved.
• We do not tolerate microaggressions, harassment, toxic behavior, or any conduct that makes contributors feel unsafe or unwelcome.
• Critique ideas, not people. Practice active listening. Give feedback that is clear, specific, and constructive.
• This is a safe and collaborative space — and everyone shares responsibility for keeping it that way.

Discord is our primary communication platform and the heartbeat of the contributor community. We do not expect you to be online constantly, but we do ask that you stay reasonably connected and communicative. Life happens and we understand that. What matters most is that you let us know if you need to step back.

• Stay reasonably active and engaged on Discord — check in at least a few times a week if you are able.
• If you need to step back temporarily, send a quick message to the founder or a team lead so we know what is going on.
• Respond to messages and check-ins even if it is just a brief acknowledgment — communication goes a long way.
• Contributors who are inactive for fourteen or more consecutive days without any communication may have their Discord access temporarily paused.
• Returning after a break is always welcome — just reach out and we will get you back in.

First Official Concept

Cioré Phone Mockup

This is the first official concept view of the Cioré phone. It is being shared internally to give contributors a visual reference for the current product direction, industrial design language, and overall feel of the device.

This concept represents an early but intentional design milestone. As prototype development continues, some details may evolve through engineering, sourcing, usability, and materials decisions.

• Pervasive data exploitation: phones and apps track location, behaviors, and contacts, monetizing users as products rather than customers.
• Forced financial upgrades: performance throttling and unsupported OS versions push users into buying new $800–$1,200 phones every 2–3 years.
• Massive e-waste: 62 million tonnes of e-waste were generated in 2022, projected to reach 82 million tonnes by 2030, with only ~22% formally recycled.
• Unethical supply chains: many phone batteries depend on cobalt and nickel from conflict zones and child labor-heavy mines.
• Hidden environmental costs: producing one smartphone can emit as much CO2 as driving ~100 miles, while devices often end up landfilled prematurely.

Organizations handling sensitive information face serious risks from mainstream consumer phones:

• Employee Data Leaks: staff mixing client data with ad-tracking apps and unvetted cloud backups creates constant exposure risk.
• Compliance Challenges: standard phones log and sync heavily, making GDPR, HIPAA, and financial compliance audits painful and expensive.
• Targeted Executive Attacks: C-level leaders face SIM swaps, phishing, and spyware aimed at deal intel and strategic plans.
• Client Trust at Risk: a single leaked call, message, or document can destroy years of professional reputation.
• Remote Teams Exposed: staff on untrusted networks relying on tracker-loaded devices creates organizational blind spots.
• Rising Insurance Premiums: cyber insurers raise rates or deny coverage when fleets rely on generic consumer devices without verifiable hardware-level security.

The Cioré phone draws its design language from luxury car UI: tactile precision, understated premium materials, clean surfaces with functional depth, and controls that feel intentional rather than decorative. Every edge, curve, and surface is considered.

The primary structural body uses strong recycled tempered glass on the front and back rather than fully biodegradable casings. Biodegradable materials are not structurally appropriate for phone surfaces. Recycled glass is.

• Thickness: 0.6–1.0 mm tempered glass panels front and back.
• Source: 60%+ post-industrial or post-consumer recycled glass cullet.
• Chemically strengthened using ion-exchange in salt baths, similar to modern Gorilla Glass.
• Commercial recycled glass protectors demonstrate equal or better drop resistance than virgin glass, with up to ~60% reduction in carbon emissions compared to virgin glass production.

Nanocellulose (nanofibrillated cellulose from wood pulp or agricultural waste) is used as a thin reinforcement and bonding layer over or under the glass.

• Fibers under 15 nm in diameter form strong hydrogen-bonded networks with high tensile strength.
• When applied as an approximately 0.1 mm coating, it can increase toughness by 20–50% and reduce crack propagation while preserving 88–92% optical clarity.
• Research shows nanocellulose composites can serve as transparent, flexible substrates in optoelectronics including displays, solar cells, and touchscreens.
• Full nanocellulose reinforcement is a Phase 2+ enhancement. Early prototypes use standard tempered glass with partial coatings to reduce risk.

Instead of permanent adhesives, Cioré uses screw-only primary assembly plus minimal bio-adhesives only where necessary. This is modeled on Fairphone 5, which achieved a 10/10 iFixit repairability score using mainly screws and clear module labels.

Recommended screw type: M1.6–M2.0 Torx (6-lobe) pan-head machine screws in 18-8 (A2) stainless steel. Benefits: corrosion-resistant, RoHS-compliant, low profile, high torque without stripping. Bio-adhesives (chitosan-aloe or cactus mucilage) used for light edge sealing where needed. These are water and heat removable, reducing harmful solvent use.

• Battery module (Nyro pack)
• Camera module (two-lens ribbon)
• Speaker and audio module
• USB-C port board and vibration motor assemblies

Modular design dramatically extends device life, reduces e-waste, and enables future upgrades (higher-capacity batteries, improved camera modules) without replacing the full device.

The display targets a semi-transparent OLED aesthetic with deep blacks, high brightness, and visible internal depth. Fully transparent production-grade MicroLED is still experimental. The practical plan:

• Phase 1–2: High-quality standard OLED with design treatments (printed graphics, selective tint, under-glass visuals) to create the floating, transparent effect.
• Phase 3+: Explore transparent OLED and MicroLED modules as production costs decrease.
• Layer stack: Recycled glass substrate, OLED display, touch layer, thin cactus/nanocellulose thermal pad.

• Volume Strip: Vertical capacitive zone on one side. Swipe up or down to adjust volume with haptic feedback.
• Power Bar: Top capacitive bar. Tap to wake or lock. Long-press for the power menu.
• Battery Mode Toggle: Capacitive slider on the opposite side to select between full charge, 80% limit, or power-saving mode.
• All controls use capacitive sensors combined with haptic and audio feedback for full accessibility.

Rear Camera: Two-lens system in a vertical ribbon aligned with the asymmetrical curve. Flush with back surface (no large camera bump). Focus on cinematic quality and low-light performance rather than spec-sheet numbers.

Front Camera: Centered, under-glass or under-tint camera that is visually minimized when not in use. True under-display is emerging; treat as Phase 2+ if cost restrictive.

Back Panel: Dark smoked black tint that appears opaque at first glance but reveals internals and soft lighting under strong light or certain angles.

Logo Glow: A controlled glow aperture with low-power LEDs for breathing notification presence, fully user-controllable and disable-able. Energy use is kept under 1% daily drain for idle glows.

Lumé is the operating system that powers the Cioré phone. It controls how the phone starts, how apps run, what data they can reach, and how everything is presented to the user.

The near-term version of Lumé OS is built on a hardened AOSP foundation — AOSP being the open-source base that many operating systems build on. This is not a cosmetic skin and it is not a generic Android setup. It is a hardened, deeply customized environment where Cioré controls the privacy model, the permissions system, the user interface, and the system behavior from the ground up.

This approach allows Cioré to ship a working, secure prototype faster and on real devices, without spending years building infrastructure that already exists in proven form. Over time, Lumé OS will evolve toward deeper platform independence as resources and scale allow.

• Starts the phone and talks to the hardware through a hardened, verified boot process.
• Runs the privacy enforcement layer that controls which apps can access what, and when.
• Shows the Cioré user interface: home screen, privacy dashboard, notifications, and core apps.
• Controls what apps can see and do, instead of trusting them by default.
• Keeps data on the device as much as possible and limits how much ever leaves.

Lumé OS is built in layers. The hardened AOSP base handles hardware communication, drivers, and core system stability. Cioré builds the privacy layer, user interface, and app policy system on top of that foundation. Each layer has a specific role and does not bypass the others.

Not all apps are treated equally. Lumé OS uses a three-tier model to give users strong privacy protection while still supporting a useful app ecosystem.

Security is enforced through sandboxing, permissions, encryption, and verified boot. Apps must request access to sensitive features. Permissions can expire and be reset. The system prevents unauthorized data access and ensures the integrity of the device at every layer.

Every user gets a plain-language privacy dashboard that shows what each app has accessed, what it is currently allowed to do, and how to change those settings. There are no hidden permissions and no buried toggles. Access is explicit, time-limited where appropriate, and always visible.

• Users can allow access once, allow temporarily, or deny access permanently.
• Permissions reset automatically over time unless the user chooses to make them permanent.
• Apps cannot access device identifiers, location, contacts, or media without showing a clear reason.
• The privacy dashboard surfaces any unusual or unexpected access attempts.
• Gaia-X, Cioré's on-device AI, is strictly local and never sends data outside the device.

• OS engineers handle AOSP base builds, hardening, and system boot.
• Privacy layer engineers build Cioré's custom permission and enforcement systems.
• Security engineers design sandboxing, verified boot, and threat response.
• UI engineers build the Cioré interface, privacy dashboard, and user experience.
• App developers build Tier 1 native apps and manage the app policy framework.
• Android compatibility engineers manage the isolated Tier 3 container layer.
• Hardware engineers align OS builds with device-specific components and drivers.
• DevOps engineers manage build pipelines, OTA hosting, CI, and code infrastructure.
• Documentation contributors support contributor onboarding and system clarity.

Full AOSP builds are resource-intensive. A standard laptop cannot handle them. The OS program requires dedicated infrastructure from the start.

• Build server or high-memory workstation required — full builds take 1–3 hours on appropriate hardware.
• Cloud build server: approximately $300–600/month, or a one-time investment in a dedicated workstation ($3,000–5,000).
• OTA update hosting: approximately $50–100/month for serving system updates to devices.
• Code hosting and CI pipeline: approximately $50–100/month.
• Reference hardware: 3–4 Pixel devices at $800–1,200 total, plus 1–2 spare units at $300–400 for flashing and recovery testing.
• Pixel 8 or Pixel 9 is the recommended starting point: unlockable bootloader, full AOSP support, and strong precedent from GrapheneOS.

• App Distribution — A secure, verified method for distributing and updating apps outside of mainstream app stores.
• Developer Tools — Documentation, build guides, and contributor tooling needed for onboarding and productivity.
• Update System — Signed, verified OTA updates with rollback capability. Users see plain-language changelogs for every update.
• Hardware Support — Pixel devices as primary reference hardware, with a clear path toward Cioré's own hardware as the platform matures.
• Performance and Accessibility — System must be optimized for real-world speed, battery life, and usability across all user types.

• Ethically sourced battery chemistry, avoiding cobalt and conflict lithium.
• Modular, user-replaceable battery packs with straightforward swap access.
• Solar-assisted charging: integrated photovoltaic layers supplement but do not replace wired charging.
• Intelligent load balancing, HeatSafe thermal management, and optional Gaia-X power advice.

Cioré phones are solar-assisted, not solar-powered. This distinction is technically accurate and sets honest expectations for contributors, engineers, and customers.

• In good outdoor light, Nyro can provide 5–20% of daily energy needs, extending battery life by several hours or slowing drainage.
• Transparent PV modules integrated into back glass can reach 14–20% efficiency and charge at slow but meaningful rates under direct sunlight.
• Indoors and in low light, gains are smaller (a few percent per day) but still reduce grid dependence.
• Wearable examples such as EcoFlow solar accessories demonstrate 3–4 hour full-phone charging under favorable conditions, showing what expanded solar surface can achieve.

• Cactus biopolymer sheets used as thin, partially transparent heat spreaders around the battery and SoC.
• Composites doped with graphene or boron nitride can significantly increase thermal performance beyond what pure cactus mucilage provides.
• Target conductivities of 10–20 W/mK are achievable in advanced composites; actual values depend on filler loading and processing.
• Graphite or copper heat spreader foils supplement cactus sheets where needed.
• External surface temperature target: under 45 degrees Celsius under heavy load, closer to 40–42 in typical use.

Battery modules are user-swappable via screws or magnetic latching. Spent modules are returned through a take-back program for disassembly, material recovery, and safe handling.

Phase 3+ aspiration: Nyro modules could power off-grid accessories or small community energy hubs.

A dedicated Radio Mode within Lumé OS where users press and hold to transmit voice and release to listen. Transport options: BLE/Wi-Fi Direct mesh for nearby use, or LoRa-class hardware for longer-range compressed voice or voice-note-style messages. Private group communications use pre-shared or QR-scanned encryption keys. Technically feasible with modern SoCs and additional radio hardware where required.

A multi-band receiver front-end enables the phone to receive emergency broadcasts without any network connection:

• FM radio bands (87–108 MHz).
• AM radio where relevant.
• NOAA Weather Radio (162 MHz band in the US).

Broadcast Mode in Lumé displays a simple tuner or preset station list. Works fully offline with no OS or cloud connection required. Nyro battery capacity is similar to dedicated emergency radios (2,500–4,000 mAh), making receiver integration feasible.

• No default data scraping or behavior logging. All training data is clearly sourced, consented, or synthetic.
• On-device learning and personalization stays entirely local.
• Federated learning with differential privacy may be used if improvement data is collected in the future.
• Users can fully disable Gaia-X or restrict it to offline-only features.

• Models are quantized (8-bit or lower) and pruned to minimize inference energy costs.
• Gaia-X coordinates with Nyro: reduced activity below battery thresholds, no heavy inference when device temperature is elevated.

• Recycled glass reduces carbon emissions by approximately 60% vs virgin glass production.
• Modular design extends device life and reduces replacement frequency, significantly cutting e-waste contributions.
• All modules use standardized screws and labeled components to support a circular repair economy.
• Designed for disassembly: at end-of-life, all modules can be separated, materials recovered, and battery chemistry safely handled.

Cioré is in an active foundation-building and growth phase. We are strengthening the contributor experience, refining public-facing presence, growing the waitlist, preparing for strategic outreach, advancing prototype research, and laying the groundwork for future Lumé OS execution. Every area of the company is moving — some faster than others, and all intentionally.

These are the areas where work is currently happening. If you see something aligned with your skills and have bandwidth to support, reach out on Discord. Support in all areas is optional and contributor-driven.

The next major project area is Lumé OS development. This work is being approached intentionally and is not being rushed. Some groundwork already exists, the vision is clearly defined, and execution will deepen once the right support structure and contributors are in place. We would rather move carefully on a project of this importance than move fast in the wrong direction.

Lumé OS is Cioré's privacy-first operating environment. It is planned as a hardened, deeply customized system built on an open foundation. The near-term direction uses a hardened AOSP-based path for practicality and hardware support. Cioré's long-term direction is greater platform sovereignty over time. Lumé OS will control privacy rules, permissions, user experience, and system behavior at every layer — and the project is phased intentionally rather than treated as an immediate free-form build.

These are areas where contributors can express interest if aligned. These are not assigned positions — they are the kinds of people and skill sets that will strengthen future Lumé OS work when the time is right.

If any of these areas align with your skills or interests and you have bandwidth, raise your hand on Discord. No pressure, no commitment — just let the team know you are available and interested.