# Learning Palantir Foundry 🚀 Action Types are what decisively separate Foundry from read-only BI. Approvals and assignments become safe, validated, structured writes. 📌 Title and Feature URL Title: アクションタイプ URL: 📝 Overview An Action Type defines a set of changes a user can apply to ontology objects, properties, and links in a single transaction. It encapsulates both the data modifications and any side effects triggered on submission, letting users think in terms of overall goals rather than individual property edits. 🔧 How It Works - Write-back to the ontology: when an action runs, all changes are committed to the ontology and reflected across every app. The latest object data, including user edits, is captured in the object type's write-back dataset. - Parameters and defaults: parameters standardize input, supporting default values, filtered dropdown results, and overrides. - Rules: define when and how an action executes, including object relationships and property constraints. - Submission criteria and validation: validation rules control execution eligibility and error handling before changes persist. - Action logs: a full audit trail of every executed action supports accountability and compliance. 🛠 Practical Usage - Run an "Assign Employee" style action that changes a role property, auto-creates a manager-employee link, and notifies stakeholders in one transaction. - Embed submission criteria like "only a director may submit amounts over 1M yen" as validation, replacing Excel-plus-email approvals with structured operations. - Reuse the same validation logic and workflow consistently across every user-facing app. 🎯 Use Cases - Standardize status changes, approvals, and assignments as permissioned, criteria-bound operations. - Let non-technical users safely execute multi-step changes spanning several objects. - Use the action log of every operation as an audit trail for internal controls. ⚠️ Caveats - Actions execute only after passing their validation rules, so submission-criteria design drives the quality of your controls. - Changes propagate immediately across the ontology and all apps, so do not leave rule and parameter design ambiguous. #PalantirFoundry# #Ontology#

# Learning Palantir Foundry 🚀 Put business logic right on the ontology. Functions cure the "numbers don't match across departments" problem by centralizing logic in one place. 📌 Title and Feature URL Title: ファンクション URL: 📝 Overview Functions let you write server-side logic that executes in isolated environments, powering operational apps like dashboards and decision-support tools. They are designed to work with Foundry ontologies, so they can read object properties, traverse links, and perform flexible ontology edits. 🔧 How It Works - Supported languages: TypeScript (full feature support) and Python (beta, with growing support especially for serverless and deployed execution). - Serverless execution: spins up on demand when invoked and bills only during execution, with a 60-second total wall-clock timeout (30s CPU plus a 30s network buffer). Multiple versions can run simultaneously, making upgrades safer. - Deployed execution: reserves dedicated resources for cases serverless cannot meet, runs a single version at a time, and bills continuously while deployed. - Capability differences: ontology read/write, Workshop integration, and external API calls work in both languages. Pipeline Builder is Python, while model embedding and semantic search are TypeScript. 🛠 Practical Usage - Derived properties: display function-computed values as table columns. - Function-backed Actions: implement complex edits spanning multiple objects. - Workshop integration: run functions to compute or display variables. - API gateway: invoke query functions programmatically to reuse the same logic everywhere. 🎯 Use Cases - Implement derived-KPI logic once and return identical results to Workshop, OSDK, and the API. - Query external systems to enrich ontology objects. - Build complex validation or bulk updates as function-backed Actions. ⚠️ Caveats - The 60-second timeout applies uniformly across execution modes, so optimize for efficiency. - Available capabilities depend on the invocation context (for example, model embedding and semantic search are TypeScript only), so decide on language early. #PalantirFoundry# #DataEngineering#

# Learning Palantir Foundry 🚀 "How many screens do I need to open just to understand one customer?" Object Views answer that pain by bundling everything about a single object into one screen. 📌 Title and Feature URL Title: オブジェクトビュー URL: 📝 Overview Object Views act as the central hub for everything related to a specific object. They consolidate properties, linked objects, metrics and analytics, dashboards, and operational applications into a single unified interface. For example, an Airport object view can integrate flight timelines, delay-handling workflows, and location data in one place. In practice, an Object View becomes the daily "home screen" that frontline users open to start their work. 🔧 How It Works Object Views are highly configurable by builders: - They support multiple formats and sizes, so appearance and interaction patterns can be tailored to the task. - They combine properties (attributes), linked objects, metrics, analytics, and dashboards into one display. - They can be embedded throughout the platform wherever the object appears. - Configuration happens in the Ontology Manager under the "Object views" tab, and version tabs at the top let you switch between format variations. - Selecting "Edit views" opens the configuration editor or the underlying Workshop module. - The system also supports version management, panel variations, commenting, and Marketplace product integration. 🛠 Practical Usage - In Ontology Manager, select the target object type and use the "Object views" tab to preview and configure. - Lay out core information, related objects, operation history, and embedded dashboards so everything the team needs is on one screen. - Beyond viewing, embed action types so users can trigger status changes or assignments directly from the view. - Create multiple formats to show different layouts per role (for example, sales view vs. maintenance view). 🎯 Use Cases - Customer 360: one launchpad combining transaction history, inquiries, related orders, and account owners for sales. - Equipment record: a maintenance home screen with sensor values, service history, related parts, and open tickets. - Case management: a single view of stakeholders, due dates, approval status, and next actions on a case object. ⚠️ Caveats - Views depend on the quality of the underlying ontology modeling (object types and link types); a weak foundation limits view quality. - Overloading a view confuses users, so design role-specific layouts that show only what each role needs. - Editing requires appropriate permissions to the Ontology Manager and the underlying Workshop module. #PalantirFoundry# #DataPlatform#

# Learning Palantir Foundry 🚀 The first move that turns a dataset into a business object. How you design Object Types largely decides downstream app performance and UX. 📌 Title and Feature URL Title: オブジェクトタイプ URL: 📝 Overview An Object Type defines the schema for a real-world entity or event. A single occurrence is an object instance (e.g., employee "Melissa Chang"), while a group is an object set (e.g., all tenured employees). This mirrors how datasets handle rows and filtered row collections. 🔧 How It Works - Primary keys and identity: objects need a primary key to uniquely identify instances. Mapping a data source to the object type lets you create and display objects in applications. - Properties: define an object's characteristics, with options such as edit-only properties, required properties, and shared properties reused across multiple object types. - Property types: support time series data, geospatial information, and struct types (nested, complex properties). - Display and search: title/display settings and search indexing improve discoverability inside apps. - Value Types: custom value types with versions, permissions, and constraints standardize representation across the ontology. 🛠 Practical Usage - Connect an employee directory or enterprise data to an Employee object type, converting raw datasets into actionable ontology instances. - Nail down primary key design first and index for search to secure downstream app performance and UX. - Use struct properties to auto-map hierarchical data, combined with shared properties for reuse. 🎯 Use Cases - Turn a customer master into a Customer object so the whole company shares one identity. - Model sensor-equipped assets with time series properties to retain operating history. - Model sites and stores with geospatial properties for map-based search and aggregation. ⚠️ Caveats - Primary key design, property types, and search indexing largely determine later app performance and UX, so treat them as your most important modeling decisions. - You must correctly map a data source to the object type before objects can be created or displayed. #PalantirFoundry# #Ontology#

📌 Important update — please read through📌 📌 少し長めですが、ぜひ読んでください📌 ------------------------------------ この度、弊社および本人にて確認したところ、一部の個人または団体により、HaneAmeの外見・署名風のデザイン・商品構成・公式ウェブサイトの構成等を著しく模倣する行為が確認されました。 これにより、一部のファンの皆様に誤解を与えてしまう事例が発生し、ご本人ならびにブランドに支障をきたす状況となっております。 日頃より HaneAme をご愛顧いただいております皆様に、心より感謝申し上げます。 今後さらなる混乱を避けるためにも、HaneAme公式のアカウントおよびウェブサイト（リンク記載）をご確認のうえ、正規の情報をご利用いただきますようお願い申し上げます。 なお、HaneAme ブランドは2025年2月に米国にて正式に商標登録されており、名称やデザイン等はすべて法的に保護されております。 創作者が注いだ努力と価値を守るため、今後とも皆様のご理解とご協力をお願い申し上げます。🙇‍♀️🙇‍♀️❤️ OFFICIAL🔻 ------------------------------------ We have recently become aware that certain individuals and groups have been closely imitating HaneAme’s appearance, signature style, product designs, and even the layout of her official website. These actions have led to confusion among some fans and caused disruption to both her personal image and brand. I truly appreciate all the love and support you’ve shown to HaneAme over the years. To help prevent further misunderstanding, please make sure to follow only the official accounts and website links (provided below). All authorized products and event information will be published exclusively through my official platforms. Please also note that the HaneAme trademark was officially registered in the United States in February 2025, and all brand-related designs and names are legally protected. Thank you for staying alert and helping protect the value and effort creators put into their work. 🙇‍♀️🙇‍♀️❤️ -------------

Sakana AI CEOの David Ha（@hardmaru）が、Tim Romero 氏のポッドキャスト Disrupting Japan Podcast に出演しました。 日本におけるAIの未来は、米国や中国とは少し違った形を取り得るのか。Sakana AIの内側から何が見えているのか。そうしたテーマで、長めの対談を行っています。 Davidは、Sakana AI の事業展開戦略、メガバンクとの取り組みがPoCから本番運用へと進みつつある現状、巨大なフロンティアモデル一つに依存するよりも複数のモデルを束ねるオーケストレーションのほうが長期的には合理的であるという見方、そして実務における「AI主権」とはスタック全体を自前で所有することではなく、グローバルなサプライチェーンの中で、AIを国内で開発・適応・運用していく能力を確保することだと、Davidは語りました。 対話のなかでは、当社の研究成果やプロダクトにも多く触れました。Sakana Fuguは、強化学習で訓練したオーケストレーションモデルで、複数ステップのタスクを多様なLLMに振り分けます。Namazuは、日本の知識や価値観を反映するようにポストトレーニングを施した、オープンウェイトモデルのシリーズです。東京のRSI Labは、The AI Scientistから続く取り組みとして、再帰的自己改善とAIによる科学的発見を専門に扱う研究組織です。共同創業者のLlion Jonesは、Transformerそのものを超えるアーキテクチャの探求という、より長期的な目標を追い続けています。 最後に「日本について一つだけ変えられるとしたら」と問われたDavidの答えは、「希望（hope）」でした。 「皆が集団として希望を感じていることが必要だと思います。その希望こそが、物事を動かしていく。日本に希望をもたらすのは何でしょうか。お金でしょうか。減税でしょうか。社会保障の充実でしょうか。おそらく、そのどれでもないはずです。もし魔法の杖を一本持てるとしたら、日本の人々が未来をもっと楽観的に捉えられるようにしたい。希望によって変化が起こり、その変化がさらなる希望をもたらすのではないでしょうか。」 ⸻⸻⸻⸻⸻⸻ Our CEO David Ha joined Tim Romero on Disrupting Japan Podcast for a long conversation on how the future of AI may take a different shape in Japan than in the U.S. or China, and on what that looks like from inside Sakana AI. David walks through Sakana AI’s go-to-market strategy, how Japanese megabanks have moved real AI workflows from proof-of-concept into production, why orchestration across many models is likely to win out over a single massive frontier model, and what sovereign AI actually means in practice: not owning the entire stack, but having the capability to develop, adapt, and run AI domestically as part of a global supply chain. The conversation also covers the research directions behind the company. Sakana Fugu is our orchestration model, trained with reinforcement learning to route multi-step tasks across a variety of underlying LLMs. Namazu is our line of post-trained open-weight models tuned to reflect Japanese knowledge and values. The RSI Lab in Tokyo is dedicated to recursive self-improvement and AI-driven scientific discovery, continuing the work that began with The AI Scientist. And our co-founder Llion Jones keeps pushing on a longer-horizon goal of moving beyond the Transformer architecture itself. Asked at the end what one thing he would change about Japan, David’s answer was “hope.” “To really move the needle in terms of innovation, like the era in Japan when you have companies like Sony or Panasonic come out, there are a few factors. One is that the nation needs to have a collective sense of hope. A nation needs to feel hopeful. It could be poor. Everyone can be dirt poor, but they have hope. And that hope leads to things being done. So, what creates hope in Japan? Is it more money? Is it less taxes? Or is it more benefits? Probably not. I think it’s stories and narratives. If I have a magic wand, if the population in Japan is more optimistic about the future of this country, suddenly they’re persuaded, to be more optimistic. People should be optimistic. With optimism comes change. And change leads to more optimism.” Listen to the full episode: 🎏